Ham Radio 2000 #1

home *** CD-ROM | disk | FTP | other *** search

/ Ham Radio 2000 #1 / Ham Radio 2000.iso / ham2000 / packet / baycom / baycom15 / termhelp.scc < prev

Wrap

Text File | 1992-03-20 | 142.4 KB | 4,016 lines

AKTUELL 11165 ALTER 11579 ANSWER 13350 AUTOROUT 14213 BADRESS 15017 BAYCOM 15558 BAYCOMNODE 16200 BEACON 18881 BELL 19328 BITSTUFF 19586 BLINK 20439 BOARD 21168 BOX-DIR 23059 BOX-LIST 25012 BOX-LOG 25921 BOX-READ 26237 BTEXT 27479 BUFFER 27751 BULLETIN 28417 CARRIER 29264 CBELL 29985 CD 30382 CHANNEL 30776 CHECK 31408 CLEAR 33331 CNOT 33646 COMBASE 34013 COMINT 34696 COMMAND 35449 CONNECT 36046 CONTENTS 36651 CONVERSE 37549 COPYRIGHT 38249 CPU 38671 CRTSAVE 39455 CSTATUS 40048 CTEXT 40390 D1LINES 40798 D2LINES 41230 DAMA 41662 DB-FORWARD 42281 DCALL 42963 DCD 43287 DESTINAT 44924 DIEBOX 45648 DIGIPEATER 48142 DIR 49097 DISCONNECT 49752 DISCTIME 49992 DISTRIB 50321 DOSCLEAR 51091 DUPLEXDIGI 51459 DWAIT 52223 DXL-BOX 53304 DXL-GATE 56108 ECHO 58033 EDIT 59367 ENGLISH 59704 ERASE 60064 EXITLOG 60935 FILES 61856 FIND 64166 FLEXNET 64947 FORWARD 66706 FRACK 67574 FREE 68087 GATE 68383 GATEWAY 68696 GERMAN 68986 HARDWARE 69785 HBAUD 70056 HDLC 70621 HELP 71003 HENNING 71589 HOP-TO-HOP 72167 INFO 72966 INI-COMMAN 73330 INIWRITE 74466 INSMODE 75182 IPOLL 75563 KANAL 75893 KEYS 77013 KNAX 77936 L2.EXE 78315 L2CTEXT 78784 LIFETIME 79155 LINK 79598 LINKROUTER 80202 LINKTIME 80614 LIST 81046 LOG 81228 LTASKS 81549 MAIL 82912 MAILBOX 83393 MANUALS 84193 MAXFRAME 84498 MBUFFER 84868 MCALLS 85590 MHEADER 85982 MHEARD 86258 MODEM 87131 MONITOR 87917 MOUSE 88495 MSELECT 89369 MSG 90186 MYBBS 90679 MYCALL 91063 NAME 91635 NETNODE 91964 NODE 92885 NODES 93600 NODECONV 94426 NODECSTAT 95328 NODELINKS 96233 NODEUSERS 97892 NRZI 99357 OFF.COM 99855 OSHELL 100381 PACLEN 101080 PARA.EXE 101489 PARMS 102095 PASSWORD 102542 PATH 103125 PRINTER 104064 QTEXT 104731 QTH 105180 QUIT 105514 RANGE 106083 RBUFFER 107691 RCMD 108182 READ 108774 REMOTE 109211 REPLY 109558 RESPTIME 110367 RETRY 110806 RMNC 111038 RPRG 111324 RS232 111677 S&F 112321 SATTRIB 112591 SAVEPORTS 113616 SCC-CARD 113903 SCC.EXE 114364 SCC.INI 114895 SCC.PWD 115790 SCCBASE 116093 SCCINT 116718 SCREEN 117463 SEND 118111 SOFTWARE 119441 SPEAK 119701 SSID 120536 ST 120993 ST-MACROS 123238 STATUS 124334 STATUSLINE 126448 SUPPLIES 127296 SYSTEM 128131 TAIL 128729 TALK 129116 TBUFFER 129627 TELL 130230 TERM-COMM 130943 TERMHELP 132096 THENET 132680 TIME 135028 TINFO 135296 TNC-COMMAN 135627 TQUIT 136764 TRANSFER 137050 TXDELAY 138025 UNPROTO 138457 USAGE 139234 USERS 140012 USER-ROUTI 140359 VADAPTER 140879 VERSION 141435 VIEW 141568 VCOLUMNS 141880 VLINES 142412 WPRG 143144 WRITE 143694 WWRAP 144023 XCONNECT 144520 Z8530 145061 INDEX 2720 \\INDEX A ^AKTUELL^ ^ALTER^ ^ANSWER^ ^AUTOROUT^ B ^BADRESS^ ^BAYCOM^ ^BAYCOMNODE^ ^BEACON^ ^BELL^ ^BITSTUFF^ ^BLINK^ ^BOARD^ ^BOX-DIR^ ^BOX-LIST^ ^Box-LOG^ ^Box-READ^ ^BTEXT^ ^BUFFER^ ^BULLETIN^ C ^CARRIER^ ^CBELL^ ^CD^ ^CHANNEL^ ^CHECK^ ^CLEAR^ ^CNOT^ ^COMBASE^ ^COMINT^ ^COMMAND^ ^CONNECT^ ^CONTENTS^ ^CONVERSE^ ^COPYRIGHT^ ^CPU^ ^CRTSAVE^ ^CSTATUS^ ^CTEXT^ D ^D1LINES^ ^D2LINES^ ^DAMA^ ^DB-FORWARD^ ^DCALL^ ^DCD^ ^DESTINAT^ ^DieBox^ ^DIGIPEATER^ ^DIR^ ^DISCONNECT^ ^DISCTIME^ ^DISTRIB^ ^DOSCLEAR^ ^DuplexDigi^ ^DWAIT^ ^DXL-BOX^ ^DXL-Gate^ E ^ECHO^ ^EDIT^ ^ENGLISH^ ^ERASE^ ^EXITLOG^ F ^FILES^ ^FIND^ ^FlexNet^ ^FORWARD^ ^FRACK^ ^FREE^ G ^GATE^ ^GATEWAY^ ^GERMAN^ H ^HARDWARE^ ^HBAUD^ ^HDLC^ ^HELP^ ^HENNING^ ^Hop-to-Hop^ I ^INFO^ ^INI-COMMAN^ ^INIWRITE^ ^INSMODE^ ^IPOLL^ K ^KANAL^ ^KEYS^ ^KNAX^ L ^L2.EXE^ ^L2CTEXT^ ^LIFETIME^ ^LINK^ ^LINKROUTER^ ^LINKTIME^ L ^LIST^ ^LOG^ ^LTASKS^ M ^MAIL^ ^MAILBOX^ ^MANUALS^ ^MAXFRAME^ ^MBUFFER^ ^MCALLS^ ^MHEADER^ ^MHEARD^ ^MODEM^ ^MONITOR^ ^MOUSE^ ^MSELECT^ ^MSG^ ^MYBBS^ ^MYCALL^ N ^NAME^ ^NETNODE^ ^NODE^ ^NODECONV^ ^NODECSTAT^ ^NODELINKS^ ^NODES^ ^NODEUSERS^ ^NRZI^ O ^OFF.COM^ ^OSHELL^ P ^PACLEN^ ^PARA.EXE^ ^PARMS^ ^PASSWORD^ ^PATH^ ^PRINTER^ Q ^QTEXT^ ^QTH^ ^QUIT^ R ^RANGE^ ^RBUFFER^ ^RCMD^ ^READ^ ^REMOTE^ ^REPLY^ ^RESPTIME^ ^RETRY^ ^RMNC^ ^RPRG^ ^RS232^ S ^S&F^ ^SATTRIB^ ^SAVEPORTS^ ^SCC-Card^ ^SCC.EXE^ ^SCC.INI^ ^SCC.PWD^ ^SCCBASE^ ^SCCINT^ ^SCREEN^ ^SEND^ ^SOFTWARE^ ^SPEAK^ ^SSID^ ^ST^ ^ST-Macros^ ^STATUS^ ^STATUSLINE^ ^SUPPLIES^ ^SYSTEM^ T ^TAIL^ ^TALK^ ^TBUFFER^ ^TELL^ ^TERM-COMM^ ^TERMHELP^ ^TheNet^ ^TIME^ ^TINFO^ ^TNC-COMMAN^ ^TQUIT^ ^TRANSFER^ T ^TXDELAY^ U ^UNPROTO^ ^USAGE^ ^User-Routi^ ^USERS^ V ^VADAPTER^ ^VCOLUMNS^ ^VERSION^ ^VIEW^ ^VLINES^ W ^WPRG^ ^WRITE^ ^WWRAP^ X ^XCONNECT^ Z ^Z8530^ \\INDEX ---dummy--- *************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** **************************************************************************** ****** This Block a is Space Holder to allow for further Indexing ********** **************************************************************************** Advice for the Building of the BayCom-Help File: ------------------------------------------------ - The File is placed after the Key Words. - Each Key Word may have max. 10 Chars in length and must begin with a Letter. - The Text for an Key Word to be at all times preceded with \\ (2 Back slashes) and followed by the Key Word. - The Text should be arranged at all times to be no more than 18 Lines per Page. The last Page (A single page Text IS ALSO THE LAST) may only have a maximum of 17 Lines, otherwise the next Page will be 'botched', which will lead to an Error Report ("unguenstige Seitenlaenge" illegal Page length. by PARA -H) - At the Beginning and End of each Page for better viewing it should be adhered to, that there is an Empty Line. Empty Lines at the end of the last Page are not necessary. PARA -H will report, if they lead to needless Page re-organisation. It should also be noted that with 2 or more Page Text,lines 1. 18 and 19 etc. should remain empty, so that they will not be corrupted in the corners of the Window. - The Lines may not be longer than 69 Characters, the rest will be disregarded. (Translator discovered that it safer to substitute 66 for 69) - Keywords Words must be written at all times between Carets. From these a Cross-Reference to other Sections in the Help File is possible. These will switch to another Optional Box, should there be an enthusiastic Requirement for this. - No Carets may be contained in the Text (Also not in this Text, therefore no example of what a Caret looks like). - After alteration of the Text, UNQUESTIONABLY a Start of para -h must follow. The File is then adapted for the insertion(s). Error Messages should be seriously collected, for those Texts which do not look healthy. !!! !! For the Indexing there must be sufficient room at the !! beginning of the File. If this is not the case, then the !! Contents will be rigorously overwritten. If, therefore the !! Asterisk-Block at the beginning of the File does not have at !! least 28 Lines, it advised that, with Block Copy to enlarge !! further the Lines of Asterisks **************************************************************************** ******** after here the individual Helptext begins: ********* **************************************************************************** \\AKTUELL ╔════════════════════════╗ LATEST UP-DATE ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ Issues the latest development. A file will be read from the Disk, that has been saved by the Sysop under the Name :- AKTUELL.SCC. If no File is to hand, there follows a corresponding Report. \\ALTER ╔══════════════════╗ ALTER <Parameter Name><Value> ║ Only for ^DXL-Box^ ║ ╚══════════════════╝ This Command allows one of the pre-Installed Parameters, to be altered unaided, to accommodate the individual's requirement. Every 'alterable' Parameter has a representation, which follows Command Word ALTER, from then on the new Value of this Parameter is operative . The following Parameters are able to be altered by the User: - ALTER LINES Number of Lines, after which the System's Output stops and then after the issue of an empty Line carries on again. If 0 is given, the Output is not stopped. - ALTER FORWARD The Mailbox, to which ones own Communications should be ^Forward^ ed. - ALTER HELP Install the Help Steps. 2 is the maximum Help, 1 brief Help and 0 without Help. - ALTER EOF A Character String, which will be sent at the End of a selected Communication (max. 10 Characters) - ALTER ALIAS Up to four Call Signs, with which the Messages to the Boards of one's own choice may be read and erased. The Output of ALTER alone lists the immediate valid settings. Followed by a Call Sign, one is able to be allowed to alter the settings of another Station. The ALTER-Command can be shortened to 'A'. For further possible settings see HELP ALTER. Example: a l 18 (ALTER LINES) Page Stop after every 18 Lines a a dl8mbt dg3rbu (ALTER ALIAS) Give Read- and Kills Permission a h 0 (ALTER HELP) Help Switch OFF \\ANSWER :ANswer ON/OFF Switches the automatic output of the personal Greeting Texts. If the Function is switched ON, then with every Connect from outside, a search will be made in the Directory for a Text File with the name <call>.CTX (e.g. DL5RL.CTX). If it is found it will be sent. If there is no Text on hand for the corresponding Call Sign, there follows no Output. With ANSWER OFF the File will not be sought, which is especially advisable with Diskette operation. *** The Files with Answer Texts able from Version 1.5 to be *** stored in a Sub-Directory named ANSWER. If this Directory *** does not exist, the Current Directory will be examined. In the pure L2-Mode (therefore without a running SCC-Terminal) no Greeting Text will be sent. Cross Reference: ^L2CTEXT^ ^CTEXT^, ^QTEXT^ \\AUTOROUT The Autorouter is a special appliance for permanently installed ^Digipeater^s, which by means of the Node software allows the memorisation of the Net topography and eases the User's choice of the respective Paths to a required end connection. Autorouter was installed at first by ^TheNet^-Nods, a progressive Form is to be found today with ^FlexNet^ and ^BayCom^-Nodes. This Autorouter measures the respective Transport time of a long Test packet to it's connected ^Linkrouter^s. This time, will have further addition(s) when sent over the Net, so that the distant Nodes will then be able to select the from time most time profitable path. The times to the End Node are able to be interrogated by the Digipeaters mentioned in the Linklists with the Destinations- Command. \\BADRESS :BADRESS <channel> <target> <mycall> [ <digichain> ] With this Command the Address for the individual Beacon will be set. The Beacon is able to be sent under an optional Call Sign <mycall>. The Call Sign <end> must not be a genuine Call Sign, it acts much more as a Symbol, that the Packet will indentify itself as a Beacon. The Output <Channel> is only relevant with an ^SCC-Card^. Example: badress 0 bake dl8mbt Cross Reference: ^BEACON^ ^BTEXT^ \\BAYCOM BayCom is an AX.25-Software, which has existed since February 1990 and stems from DG3RBU (Hardware, Documentation, Test) and DL8MBT (Software). It meets the requirements of a Terminal Part for End users and a Net Node Part called ^BayComNode^, which will be placed in individual Digipeaters in Bavaria. For operation by the End user it gives a Resident Layer-2, which takes over the Function of the TNC. This is able to be run in the Background on the Computer. By request the Terminal is able to be started, which for the User makes all the optional Functions available. SEE ^COPYRIGHT^ ^SUPPLIES^ ^MANUALS^ \\BAYCOMNODE BayCom-Node is a Net-Node-software, running on IBM-AT-Compatible Computers with a Special Expansion Card (^SCC-Card^). At this time up to 8 Radio Channels are able to be accommodated with a Maximum of 19200Bd at all times, but it is capable of yet further development. BayCom-Node runs completely resident, through which, on the same Computer the Terminal, or the OE5DXL-Mailbox and -Gate Software is able to be run. There are Principally three substantial attributes: - appears like TheNet (User Interface) - retains similarity to ^FlexNet^ (Digipeating, Router) - but has not the slightest intrinsic mutuality of both of the previously named Systems. 'via' digipeating with cut off, of the inactive paths is possible. The Auto router inserts missing Digi Call Signs, so that only the most important Paths must be given. The behaviour in this connection equals in some ways that of ^FlexNet^ 3.0. The Path to End Places (Terminals) will be taken from the MH-List, (if the case arises) which has saved the last 2047 Call Signs and with it makes possible a positive Reconstruction of the Path. The path will be saved by it, but not the complete Path. Command List for BayCom-Node: (A)ktuell Issues the latest Communications (C)onnect <call> <digi> Connection construction to <call>. (CS)tatus Users-List similar RMNC/FlexNet, see ^NODECSTAT^ (CONV)ers Switches into the ^Converse^mode (also TALK, MSG or /) (^CPU^) issues 'usage' statistics of the Node Computer (D)estinat issues known NetNodes (^DESTINAT^) (F)ind <call> searches in the MH-List for <call>, see ^FIND^ (H)elp Help text. HELP INDEX shows available Keywords. (HA)rdware issues a Description of Digipeater-Hardware. (I)nfo sends short Info text about the Digi. (L)inks shows neighbouring Digipeaters (^NODELINKS^) (LT)asks issues the Status of Task Administration (^LTASKS^) (G)ate Toggles on to the ^DXL-Gate^ (M)ail Toggles to the next located ^Mailbox^ (MAP) Issues a Display of the environs of the Digi (MH)eard Issues the latest heard Call Signs (see ^MHEARD^) (MS)g <call> .. Sends a Text to <call> (^MSG^) (N)odes Issues the System known Net Nodes (^NODES^) (P)ath <call> shows the Path to <call> (^PATH^) (PAR)ms Output of the installed Parameters (^PARMS^) (Q)uit Sever Connection (better: simple disconnect) (U)sers shows list of all immediate Users (^NODEUSERS^) (SO)ftware Issues a Description of the Digi-Software. (ST)atus Shows ^Status^ Report with internal Debugging-Date (T)alk <call> .. Sends a Text to <call> (^TALK^) \\BEACON BEacon <Channel> <Seconds> The Time in 1sec-Units decides, how often the Beacon should be sent. Beacon Transmissions are normally significant only for explicit Tests and should in all other Cases not take place. The Output <Channel> is only of importance when an ^SCC-Card^ is used. With RS232 Operation it is sufficient to issue the Time. e.g. :BE 180 Cross Reference: ^BADRESS^ ^BTEXT^ \\BELL ╔═════════════════╗ BELL ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Sysop is called with this Command if it has been enabled \\BITSTUFF Bitstuffing (Zero Insertion and Deletion) This Procedure takes care of, that in the Data of the Packets no more than 5 1-Bits are able to follow one behind the other. After the 5th Bit a 0 will be consistantly inserted, which naturally must be removed again when received. The method of this procedure is, that after the ^NRZI^-Coding, with the carry over of of a larger quantity of 1-Bits one behind the other, is able to be forced, which will be transferred as 'No Change' of the Data Management. Through the insertion of the 0-Bits will be forced a regulated change of the Management. This is necessary, in order to obtain from the received Data the Timing, (which it gives for synchronising when no transfer of Start- / Stop Bits), which is able to be extracted for synchronisation. \\BLINK ╔═══════════════════════╗ BLINK ON/OFF ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ Switches the Flashing of the ^L2.EXE^ in the upper right Corner. Sometimes it is troublesome if another Program uses this corner of the Screen, or so that the Boss is not able to see that Packet Radio is running in the Background on the same Computer. (Please do not laugh, many requests were received for this Command, and this is the reason this it is now inbuilt). The Command is able to be pre-set for better clarity and is issued only from ^SCC.INI^ it is able to be restored with ON. \\BOARD BOARD ("Blackboard", Index) As a rule a Board contains Communications, which cater for a particular Theme or Receiver. Each differs - User-Boards: The private Letterbox of the Users, Communications contained here may, as a rule only be read and erased by the Sender or Addressee (so called personal Communication). - ^Bulletin^-Boards: Open Letterbox with Communications, which everyone is able to read (therefore may only be erased by the Sender). Communication on these Boards are called ^Bulletin^s. Every Board possesses an unambiguous Name, with which it is able to be addressed. With User-Boards it is the Call Sign of the Station, to which this board belongs. With Bulletin-Boards expressive indications exist, which indicate the Theme sphere of the Communications of these Boards (e.g. "DX", "Satellites", "Nets" etc.) The Communications on the Board are serially numbered. With DXL-Boxes it is the latest Communication which is No. 1. With DieBox-Systems it is the oldest Communication. With ^Box-DIR^ as an example, ^Box-LIST^-Command the Contents of the Board beginning with Communication No. 1 will be listed. With every Board there will be a ^Lifetime^ associated with the Mailbox. The Sysop decides how many Days a Communication may stay on the Board, before it will be erased automatically. The Board operation is composed of many Commands, e.g. DIR, READ, ERASE. The DXL-Box always retains the known Name of the Board's previous User and employs it, in the case that the next Command is not an explicit known other Board Name. \\BOX-DIR ╔════════════════════════════════════════════╗ ║ DIR <^BOARD^><^Range^> Only for DXL-Box ║ ║ DIR, DIR USER, DIR ALL Only for DieBox ║ ╚════════════════════════════════════════════╝ In the ^DXL-Box^ this is the Command to List the Contents of a ^BOARD^ The optional issue ^Range^ decides which part of the Board's Contents will be output. If no Range is given then the Output will be the Complete Contents of the Board. For each Message, the following information is given: - Number of the Message (Important for ^READ^ and ^ERASE^ - Name of the ^BOARD^, from which the message has been Sent - Advice, to which Box the Message has been forwarded - Length of the Message (Quantity of Lines) - remaining ^Lifetime^ (In days) of the Message - ^Distrib^utor that is the End Mailbox of the Message - Reference (Title of the Message) The following possibilities of DIR-Command of the DXL-System are available. - DIR AFTER <Date> lists all Messages of the ^Board^, that have arrived after the given date. - DIR MESSAGES <Text> lists all Messages, in which the <Text> is contained in the title. (Without <Text> the System lists all Messages - DIR BOARDS Gives out the Names of all the ^Bulletin^ Boards - DIR USERS Supplies the Directory of all User-Boards - DIR NEWS Lists Messages, which have been received since the User last issued the Command - DIR PATH Names all known Boxes in the Forwarding (^S&F^) In ^DieBox^ Systems the Command ^Box-LIST^ is allowed This Command is also in the ^DXL-Box^, there it has the same meaning as DIR. The Command can be shortened to 'D' The DIR-Command in DieBox Systems lists the Descriptions of the ^Bulletin^-^BOARD^s (Info Files) DIR USER lists all User-Boards, DIR ALL the similar of similar Boards. \\BOX-LIST ╔═════════════════╗ LIST <^BOARD^><^Range^> ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Messages of the requested Board will be output, beginning with No. 1 (the oldest Message). The Output of the ^Range^ reduces the Output correspondingly. Failure to give a Range, causes the System to list all Messages of the Board. After every 50 Messages, the Output stops and is then able to be ended or progressed. For each Message the Box issues: - Number of the Message - Sender's Call Sign - Date of the Entry of the Message - Length (In number of lines) - Reference (Title) of the Message With the help of the Message Number the required Message is able to be read (^READ^-Command) or cleared (^ERASE^-Command) LIST is able to be shortened to 'L' \\Box-LOG ╔══════════════════╗ LOG ║ Only for ^DXL-Box^ ║ ╚══════════════════╝ Outputs a Log Book. It designates in Rows all Stations, which have already used the Box today and the time of use. \\Box-READ READ <^BOARD^> <^Range^> In all Mailbox systems the Command for the Reading of a Communication of the given ^BOARD^. Optionally it will be able to give a ^Range^. With the DXL-System it will be asked for after the Reading of a Communication to one's own Call Sign, if this Communication should be erased. A Communication remains saved in the System, until it's ^Lifetime^ has run out or an authorised User erases this Communication (Command ^ERASE^). What Communication is to to be found at this time in a Board, is shown by the Command ^Box-LIST^ in ^DieBox^-Systems for example ^Box-DIR^ in the ^DXL-Box^-System. READ is shortened to 'R'. Each Communication begins with a Header, the Sender, Length, Title, Forward-Pat and -Time (^S&F^). In DieBox-Systems it will be able to obtain through the addition of the '+'Character to the READ-Command, the complete Communication header, otherwise only the shortened form will be given. From now on an Output by DieBox is possible in the Form "$ Character Quantity" The Output then begins with the given Number Character after the Beginning of the first Communication. \\BTEXT :BText <Channel> ........text......... Beacon text. This is the Text that will be sent with every Beacon. The Qualifier <Channel> is only relevant for use with an ^SCC-Card^ Cross Reference: ^BEACON^ ^BADRESS^ \\BUFFER BUffer <Quantity> The total Quantity of Buffer Blocks, which are available for the Program. The Buffers will be managed dynamically, i.e. released and replaced after each usage. A Buffer occupies a 340 Byte Storage Unit, and is able to be used by a maximum of 330 Bytes (Overhead). The area serves as the first Line for the entrance of Data to be sent and received, and also for such things as Logbook etc. Even more Space will be used as allocation for the resident ^L2.EXE^. Therefore if too little is allocated, an overrun must be expected. Recommended: Terminal Usage 40 Buffers, NetNode 200 Buffers. \\BULLETIN A Bulletin is a "Communication to all" ("open Communication"). It is able to be read by all Stations. As a rule it is only able to be erased by the Author and the Mailbox Sysop. The Theme Area, in which the Bulletin is to be included, is to be found in a particular Bulletin-^BOARD^ ("Info-File", Rubrik). There it will be erased automatically after the run out of this boards associated ^Lifetime^. The indication of the Bulletin- Board's distribution from Box to Box is something separate. With the Sending of Bulletins; usually collective addresses will be employed, see ^Distrib^utor. In addition to Bulletins there is Communication to a particular User (so called personal Communication). They are able to be erased by the Author and the Addressee and also have a ^Lifetime^. \\CARRIER :CArrier <Channel> <decimal> DCD-Treatment: (Only relevant with an ^SCC-Card^ installed, with RS-232 Operation see ^DCD^) 0=Soft-DCD Squelch is able to be left open in operation, DCD will be produced from the DPLL of the 8530. 1=Hard-DCD DCD-Control of the 8530 will be addressed and must be served from the Modem. 2=Hardclock+soft-DCD TX-Rate will be taken from the Hardware but DPLL (e.g. for echo duplex) 3=Hardclock+hard-DCD TX-Rate will be taken from the Hardware DCD-Control (e.g. for G3RUH-Modem) 4=fullduplex Fullduplex-Operation (No DCD, Hardware-Clock) \\CBELL :CBell ON/OFF Toggles the Bell. If CBELL ON, then with Connect, Disconnect or CTRL-G sent from the QSO-Partner a sound will be produced. If CBELL OFF, then the Computer is quiet, consequently, not so many 'Klingelzeichen' (Ringing Characters) arrive. Important for 'night sleeping Times', for which one in general wishes his peace. Cross Reference: ^KNAX^ \\CD :CD <directory> Changes the Current Directory. With this Command it is able to jump to a chosen Directory, from which Data will now be able to be obtained, as opposed to the Directory from which the Software was loaded. (Also the Log-File, on the contrary to Version 1.40 Example :cd... :cd \baycom\remote Cross Reference: ^DIR^ \\CHANNEL ╔══════════════════════════╗ :Kanal <decimal> ║ Only Valid with ^SCC-Card^║ ╚══════════════════════════╝ Switches the SCC-Channel number. During an ongoing Connection this is not sensible. The setting is only valid for the immediate active Port. The Monitor will display all Channels. Used with appropriate Entries in the Link-List, normally the Channel must not be set manually. The Channel switching is only significant for the F10 Window, the Normal Method is with a Connect Command. \\CHECK ╔═════════════════╗ Check <^Range^> ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Check-Command lists all Communications of the Info-Files (^Bulletin^-^BOARD^s) in the rows following it's Entry to the Box. The Communications are sorted in Date Order, beginning with the youngest Communication. With the Output of a Range only the requested Communications will be listed (e.g. CHECK 5 lists the five newest Communications). If the Check-Command is given without a range, only those ^Bulletin^s will be listed, which have arrived since the last Log in by the User. If a '<' is issued followed by an empty Character and a Character String, the CHECK-Command lists: - all Communications of this Call Sign, if the Character String was a Valid Call Sign or is at least the beginning of a valid Call Sign - all Lines, in which the Character String of the Text is found, if it is not a valid Call Sign. If it shorter than four Characters, only the Header of the Communication, will be sought and not the Contents. CHECK is able to be shortened to C. Examples for the Usage of the CHECK-Command: C : Shows the New Entries since the last Log in C 10 : Shows the last 10 New entries under Info-Files C 2- : Shows New entries beginning with the 2 C -5 : Shows the last 5 New Entries C < DK0MAV : Shows all Entries, which have been written by DK0MAV C 2-30 < DK0MAV : Shows all Entries in the Range 2-30 which have been written by DK0MAV. C < DK : Shows all Entries, which from the Call Sign beginning with DK have been written. \\CLEAR Screen Clearance. Possible Alternatives: ---------------------- :CLear Clears the RX Window (middle Screen Window) :CLear 1 Clears the TX Window :CLear 3 Clears the Monitor Window :CLear 123 Clears all Windows \\CNOT :CNOT <call> <call> .... Creates a List of Call Signs, from which no Packets will be accepted. The Packets to and from the Stations in the List will be handled as if they were never received, therefore completely ignored. DM will not be sent However, the Packets from these Stations will be displayed on the Monitor. \\COMBASE ╔═══════════════════════╗ COMBASE <address> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ If necessary, this Command will install the Address of the COM Port. In this manner it is also able to install COM3 and COM4, or it is able to install a completely different Address, in the case where the Hardware permits. An installation of this Address also requires the installation of the ^COMINT^-Parameters. In normal operation with COM1 or COM2 this Command must be commented out by the use of a comma (;) at the beginning of the line. \\COMINT ╔═══════════════════════╗ COMINT <IRQ-Number> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ With this Command it is possible should the occasion arise, to install the Interrupt Number of the COM Port. It is by this method that COM3 and COM4 are able to be adapted. It functions however, only for Hardware Interrupts IRQ0 to IRQ7, the AT- Interrupts are not able to be utilised An Installation of this Number also requires the Installation of the ^COMBASE^-Parameter. In normal operation with COM1 or COM2 this Parameter must be commented out by the use of a comma (;) at the beginning of the Line. \\COMMAND COMmand ON/OFF This Parameter sets, whether after executing a Command from the Terminal an automatically placed Colon will or will not be at the beginning of the next Line. Users of WA8DED-Firmware are accustomed to it: that before each TNC-Command the ESC-Key has to be pressed. In BayCom with COMMAND OFF there is no Automatic colon, with ON there is. The previous setting (in the Version 1.2) was COMMAND ON, that is after each Command a Colon appeared un-requested in the next Line and had to be explicitly removed by ESC, TAB or DEL. \\CONNECT :Connect <call> <digi> [ <digi> ... ] Connect with conventional Syntax. The Empty Character following the C must be given. On Port 0 (F10) No Connection will be made, but the ^UNPROTO^ -Call will be output with Digis (similar to WA8DED-Soft). :Connect <call> <channel> Connect via a particular Channel of the ^SCC-Card^. It will be able to send on a particular Channel, without Entries in the LINKS-List a Particular. The Channel Number is given before the first Digi. It is optional, whether a Letter (A..H) or a Number (0..7) is used. \\CONTENTS The Contents of the Communications, which will be in Mailboxes of the Amateur Radio Service, is subject to limitations, which are in part instruction, part on technical requirement grounds. For the maintenance of trouble free Mailbox Operation and Communication service these restrictions should be unconditionally observed. They are these: - The Issue of the National Conditions for the Contents of Dispatches of Amateur Radio Stations - No Communication in the Binary Format (Object Code of Programs, compressed Communication Contents) - No Dispatches with a disproportionate large space requirement (e.g. coded Screen/Picture Data) - No "Open Letters" and similar Commentary (Difference of Opinions, please fight it out direct with the other OM and do not get on every one else's nerves). \\CONVERSE Converse-Mode designates a special User Form of Packet-Radio, which for a concurrent Group of Users forms a method of Multi- Converse. For this purpose they connect to a ^NetNode^ or a to a Station correspondingly equipped for that purpose. After Entry into the Converse-Mode (By issuing a suitable Command, e.g. CONV) each one of the participant's entered Lines will be sent to all other participants. Therefore when a Conference Mode is in operation a Frequency can be heavily loaded, because all Packets will be repeated many times, It forms a very good supplement for Communication in the PR method of Amateur Radio Service of ^BayComNode^ see ^NODECONV^. \\COPYRIGHT The Copyright of ALL of the Constituent Parts of BayCom belong to the Authors. These are:- SOFTWARE, CIRCUITS, PCBs, MANUALS. COPYRIGHT OWNERS :- SOFTWARE - Florian Radherr, DL8MBT HARDWARE - Johannes Kneip, DG3RBU ENGLISH MANUAL and FILES - Denis Godfrey G0KIU on behalf of the BayCom Team. SEE DOCUMENTATION FOR FULL DETAILS \\CPU ╔════════════════════════╗ CPU ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ Here will be calculated and recorded the average and immediate loading of the Computer. Present Arrangement; only the BayCom-Node Software will write to it. An eventual Mailbox will write the Processor performance by instruction. The Times will be measured in standards of 13ms (this 'crooked' value is system determined, which is be derived from the Baudrate 75Bd) and then set in Relation to the Running time of the System. The second slot records values, which in the last 40 Seconds will have been emitted and consequently, the present loading of the Computer. \\CRTSAVE :CRtsave (minutes) Activates a Screen Blanker, e.g. :crt 5 (5 = 5 minutes) After the given time in Minutes has run out with no activity having taken place: no Key pressed or no incoming Connection established, the Screen will be scrambled and a Starry Heaven will appear. With the pressing of a Key (also Shift etc.) or an External Connection being made, the Screen returns to its original state. If the Monitor Screen (F10) has been selected, the Screen will NOT be switched to the Starry Heaven. \\CSTATUS :Users ) or ) Commands are interchangeable :CStatus ) issues a List of the immediate connected Stations. Example: Port Status Call 1 Info Transfer DL8MBT > DB0AAB 2 Link setup DL8MBT-2 > DG3RBU \\CTEXT :CText <text letter> With this Command and if the Terminal SCC.EXE is running, a Standard Text will be sent to a Connecting Station, otherwise ^L2CTEXT^ will be sent. It is only a Letter that must be installed here, corresponding to a Standard Text (see ^ST^). In these Texts it is able to construct better 'adornments', and also to create ^ST-Macros^. \\D1LINES ╔═══════════════════════╗ D1lines <Quantity> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ the actual Number of the Lines in the TX Window and thereby the position of the first ^Statusline^ on the Screen. This is able to be altered optionally during operation with CTRL-HOME and CTRL-END, see ^Keys^ \\D2LINES ╔═══════════════════════╗ D2lines <Quantity> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ the actual Number of the Lines in the RX Window and thereby the position of the second ^Statusline^ on the Screen. This is able to be altered optionally during operation with CTRL-PgUp and CTRL-PgDn, see ^Keys^ \\DAMA DAMA is a Procedure for the prevention of Collisions on the User Access of a Digipeater. This procedure has been roughly specified by DK4EG, and hitherto has been implemented by DL8ZAW in the ^TheNet^Node Node Software, it still remains in the research area and could bring improvements in the future, with greater technical grasp of Users on the Digipeater. The Basic Principle is, that the Digipeater calls each User individually and possibly for that reason no User sends unrequested; therefore no Collisions are kicked out between individual Users. \\DB-FORWARD FORWARD <^BOARD^><^Range^> @ ╔═════════════════╗ <^Distrib^utor> ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Forward-Command allows the forwarding of the given Personal Communications (only from User-Boards) to another Mailbox. They will be passed on with the next Forward-Session to this Box If +E is attached to the Command Line, the given Communication will be struck out of the Forward-List. With +L issues the actual Entry of the Forward-List. Only Author or Addressee is able to forward a Communication of this Type. The shortening of the Forward-Command is 'F'. \\DCALL :DCall <call> Digipeater Call Sign. This is the Call Sign under which the Station will Digipeat. With the operation of ^BayComNode^ this Call Sign is conventionally identified with the Node Call. With Terminal operation it should be similar to ^MYCALL^ but with a different SSID. \\DCD Software-Carrier Recognition. As a substitute for a slow Squelch in the TX/RX Rig it is able, Version 1.50 for a Software Carrier Recognition system to switched on. At the Rig the Squelch is able to remain OPEN. For the reason a small ^TXDELAY^-Parameter is possible by a Connected Partner. The Software Carrier Recognition is certainly not as good as a good Squelch closure or a PLL-DCD with XR2211. Therefore the Software DCD should only be employed if a Rig with a slow Squelch is being used. The Controlling Parameter follows Command ^CARRIER^ CARRIER 0 Software DCD OFF. Triggering from the Data edge CARRIER 1 DCD will be obtained from the Data. The Triggering Recognition results from the following procedure Through the preceding ^NRZI^-Coding and ^Bitstuff^ing it is able from the Quantity of received 1-Bits to identify whether it is receiving valid Data or only noise. To decided whether the Channel is "Free" or "Occupied" will be altered according to the following criteria; X - more than 6 1-bits: Data stream invalid or Frame Reject -->X:=0, DCD will be immediately switched to 'Channel Free' - precisely 6 1-Bits: Flag will be utilised for the Beginning and End Limits of Frames and will be sent for the synchronisation at the start. For such a received Token, X will be raised by 5 - Less than 6 1-Bits, it could be valid Data that is being handled. X will be raised by 1. - X>=10 means that the Channel is 'Occupied', X<10 means Channel 'Free' \\DESTINAT ╔══════════════════════════════════╗ Destinations ║ Command for ^BayComNode^ & ^FlexNet^ ║ ╚══════════════════════════════════╝ Issues NetNodes known to the System (DESTINAT the same as NODES) The List will be retained from the constantly running ^FlexNet^- compatible ^Autorout^er. Consequently it is able to extract from it, that the listed Stations are actually accessible. D * Lists all Entries, also those which at this Moment are not accessible. D LOCAL Lists only Nodes, which at the Moment are accessible with a running time under 100sec. D <call> Shows the Way to <call> (see also HELP PATH) \\DieBox DieBox name of the developed Mailbox System from DF3AV (Nord><Link) for IBM-PC. At this time it is probably the most wide spread Mailbox System in Europe. DieBox-System requires the following Commands: ^BELL^ ^CHECK^ ^Box-DIR^ ^ERASE^ ^DB-FORWARD^ ^Box-LIST^ ^MYBBS^ ^NAME^ ^QUIT^ ^BOX-READ^ ^SEND^ ^SPEAK^ ^TELL^ ^TRANSFER^ ^USAGE^ After Logging in the following Commands are possible: (Valid Short Forms in Brackets) (C)HECK With the Check-Commands it will be able to request the new Data that is available since the last Log in. The Data Stock that is within certain Criteria (Sender, Reference etc.) is able to be sought. This Command is very powerful, with Help Check, recalls sufficient referenced Information of what is in the Mailbox. (D)IR List out all available Boards. With DIR USERS all User-Boards will be shown. (E)rase <Boardname> <Number> erase the corresponding File, but only, if it is from or to one's self. (H)elp issues Text, in which a short overview of available Commands is shown. With the issue of HELP <Command name>it is able to obtain Information on the individual Command (L)ist <Boardname> list all Entries on the corresponding Board (M)YBBS give out own Home BBS, will be automatically communicated over the PR-Net to other Boxes (Q)uit end of the Connection. (R)ead <Boardname> <Number> reads a File. Files to ones self must not be given a Boardname. Private files are placed on the Boardname of the corresponding Call. (S)end for the sending of a Message, whether to a Board or to a special Receiver (see ^Mailbox^) Giving only an S, will request all information, but it is also possible, to make all indications in one line. Example: S DF4UD @DB0CZ Digi Wegscheid Reference Address for the Forwarding (see ^Forward^) Addressee Following the output of the Text it will be necessary to follow with ***END or with a Ctrl-Z. (S)peak to select out put language of the System Reports. (U)sage shows all immediately logged on Users. U ALL shows a Log output. \\DIGIPEATER General representation for the attributes of a Station, Packets from a sending Station received and then re-transmitted again, either on the same, or on another Frequency. It is permitted that these Packet re-transmisions (Contrary to Repeaters,) by Digipeaters are permitted on the same Frequency as every other Station on PR). At the commencement of PR an outward extension of the Connection via the normal UKW-Range Channel, this form requires an extra Licence for the Digipeater (DB0...Callsign). It accepts Packets on an access frequency in the 70cm-Band, and passes these on via beamed Radio routes in the Gigahertz-Range, the backbone of today's usual PR-Net. Such durable Digipeaters themselves serve nowadays as a special Form for the dissemination of Communication, namely the so named ^Hop-to-Hop^- Digipeating and allows by this means a substantually quicker setting up of the Connection. See also ^NetNode^. \\DIR DIR <Mask> Displays the actual Directory of <Mask> following the usual DOS procedure and in the familiar format (therefore Constructions such as *.* \*.exe or similar). The Display appears in the RX (Middle) window CP/M - Friends are able to use :CAT instead of :DIR !!!! In version 1.50 an Error has crept into this Function. With certain configurations, confusion occurs and it outputs the same Characters. The remedy for this effect is not immediately to hand and hopefully will be corrected in the next Version. A repeat of the Command will be successful. Cross Reference: ^CD^ \\DISCONNECT :Disconnect Severs a Connection. A twice issued Disconnect severs the Connection immediately. :d ALL Disconnects all running Connections. This is suitable for a hurried Closure of the Program. \\DISCTIME :DISCTime <10sec-Value> The Time in 10sec-Units, after which a Connection will be Disconnected if no Data is to be conveyed. DISCTIME 0 means that Connections remains live permanently unless a ^DISCONNECT^ is initiated by either Station. Additionally if everything remains quiet. \\DISTRIB For the Addressing of Bulletins with Area Identification, here are the accepted Short Forms. @WW or @ALL (World Wide) @EU (Whole of Europe) @ALLE (German Speaking Area) @DL (German) other Country prefixes (HB, OE, F) In addition there are local Identifications e.g. @BA (Bavaria), @WEST (West Germany), @OEDL (Austria + Germany) In Case of Doubt ask the SYSOP ! Messages under WW, EU or ALL in any case should be typed in the English Language. Also please be aware of spreading Messages too widely, and make the area as small as Possible. It is not good practice to send a Message about a Youth Group Field Day of the OVs Urwald 46 to @WW...... !!! \\DOSCLEAR ╔═══════════════════════╗ DOSCLEAR ON/OFF ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ On leaving the Program decides if the Screen will be cleared (ON) or the DOS-Screen which was present before running BayCom will be restored. (OFF) \\DuplexDigi A Duplexdigi is a ^Digipeater^, which works as an FM-Relay, that is, it is able to send and receive at the same time. In general it is usual for a Digi, for all that arrives at the RX, to be transferred at the same time to it's TX. Usually, in DL it is in the 70cm-Band a bridge from 7.6MHz into the Frequency Range 438.300 ... 438.550MHz That is opposite to the conventional Digi and has the following advantages: - all Stations themselves reciprocate 'direct'. By this means all transparent transfers will be able to be read with all Outputs from everyone. Without that it must run explicitly 'via Digi'. - Reduction of Collisions. If one sends, all hear it and therefore will not go into Transmit. \\DWAIT :DWait <Channel> <10ms-Value> Waiting Time for which the Channel must remain free before being able to send. For the reduction of Collisions, the actual Value of a Contingency Time is between NUL and the doubled installed value. With normal Radios a relatively long Dead time lies between Receiving and Sending, this must be borne in mind for a correspondingly higher Contingency Value calculation. Recommended Values are between 10 and 30, according to the Channel Conditions. The method employed here is in approximate agreement with the quality of the known Persistence-CSMA Otherwise it is a fallacy to believe that with a short DWAIT it is possible to get through more quickly, Often (especially with ^DuplexDigi^-Entry) it is substantially better to use a longer Wait Time. If all others using the Channel Frequency are already ready to transmit then they are able to Collide with each other, but with a longer DWAIT lies a negligible Collision possibility. \\DXL-BOX Mailbox from OE5DXL The DXL-Box runs on a single Disk Computer with a 64B180 Processor, or in a Ported Version by OE1ATU Version on IBM- Compatible PCs. It is distributed in Austria and Southern Bavaria and is able to run, together with ^BayComNode^ on a Computer. In the Original version the Node Software from OE5DXL (so called. ^DXL-Gate^) belongs to the DXL-Box. With the ^GATEWAY^-Command it as able to switch to the Node Part of the System. Die DXL-Box recognises these Commands: ^ALTER^ ^CONVERSE^ ^Box-DIR^ ^ERASE^ ^FREE^ ^GATEWAY^ ^Box-LOG^ ^QUIT^ ^QTH^ ^Box-READ^ ^REPLY^ ^SEND^ ^TIME^ ^NodeUSERS^ Important Commands in the DXL-Box are : (A)LTER indicates the Parameter in the System (e.g. Line Number, at which the output will be stopped, Language, Home Mailbox etc.) With issue of the Command HELP ALTER to the DXL-Box reference will be made to more Information. (D)IR With this Command the Messages of the respective fixed Board will be displayed after each request. DIR BOARDS lists the contents of all Boards . DIR USERS list the contents of all User Mailboxes. DIR NEW lists all New Messages since the last Log in. (E)rase <Boardname> <Number> erases the appropriate File, but only, if it originates from or is addressed to the Call Sign of the person giving the Command. (G)ateway Change into the ^DXL-Gate^, if it is available. (H)elp outputs a Text, containing a Short overview of available Commands. With the issue of :- Help <Command Name> it is able to obtain further Information about the Command. Log Displays the Log of the day. LOG <Call> displays personal Log of the respective OM (Q)uit End of the Connection. (R)ead <Boardname> <Number> reads a File. One's own Files require no Boardname, with other Private Files the Board name of the corresponding Call is required. (S)end Sends a Message, either to a Board or to a special Addressee (see ^Mailbox^). If only an S is given, all information will be requested, it is however possible, to make all indications in one line. Example: S DL5FBD @DB0GV BayCom-Problems Reference Address for the Forwarding (see ^Forward^) Addressee At the end of the Text it will be necessary to conclude with the following:- NNNN or with a Ctrl-Z. (U)sers shows all currently logged in Users. \\DXL-Gate Net Node System from OE5DXL Originally conceived by OE5DXL for a Z180/Z80-System, the DXL-System meanwhile, has been Ported onto the PC and runs - either as a Mailbox only or as a combination of a System Mailbox and Gateway e.g. onto ^BayComNode^-NetNode. The Gateway stands as the ^Digipeater^-Part of the System, the Mailbox serves for the Storage and Readout of Messages. Through Connection to the NetNode under it's Call (without ^SSID^) one arrives in the Gateway. To request which other NetNodes of the System are known, use the Command: (L)ANS. The Computer then shows a List of Place Names, which with the C-Command it will be able to connect. Take it for example that DG9YAG in Frankfurt (FFM) is QRV, It is able to connect to him in Frankfurt by using C DG9YAG FFM. (P)ATH <LAN/CALL>. With this Command the Path to a LAN or a known Call is able to be requested. Then follows an output on an actual immediate Route, which has had the expected Link Time evaluated. (MY)LAN. It is able to achieve by the DXL-System under a LAN, the one that is to be sought, by the use of the C-Command. This Information will also be sent further to other DXL-Neighbour Nodes (^User-Routing^). The self method is always to be recommended! (T)ERMINALS <LAN> outputs a List, who has used the <LAN>. MH * outputs an MHeard-List (M)AIL. Alteration in the Mailbox-Part (C)onnect <Call> <LAN> constructs a Connection to the given call via the appropriate LAN. If the LAN is omitted, an eventual known Route will be used (self with MY) otherwise the Node reports "UNKNOWN". If it is required to connect to the User Entry of a Station, C <Call> A must be issued (A = 1. Port of the System) CONV <Number> Switches into a Converse-Net (see also ^Converse^), the following Commands are valid: /users shows Users in the Converse Mode /bye ends Converse \\ECHO ╔══════════════════════════════╗ :ECHO ON/OFF/2 ║ Echo 2 Only valid in ^SCC.INI^ ║ ╚══════════════════════════════╝ :ECHO ON/OFF decides whether or not, the Characters typed in the TX Window will be also be additionally displayed in the RX Window. If it is (ON) then the corresponding TX display colours that have been chosen will be used in the RX Window, so that the sent and received Text will be able to be differentiated. That it is a personal choice, whether the upper Window should be displayed underneath is given as a switchable function. With Remote Control the Function has another meaning: //e ...text... returns the given Text back to the QSO-Partner. This is very practical, especially for Tests of the Connection running time. * On Internal Programming Grounds, only //e is able to be typed * and NOT //echo. From Version 1.50 there is a further Installation that is possible (ONLY IN SCC.INI) ECHO 2 With this installed, in the RX Window only what has been presented after a Prompt-Character of a Digipeater or a Mailbox. In a QSO operation the Echo mostly disturbs, with mechanical operation it is able to be extremely interesting. \\EDIT :Edit <filename> Opens a Text file, in order to create a File from the Keyboard The Input from the Keyboard will not be transmitted, but will be written to the File. If a File exists with the same name, then the Text input from the keyboard will be added to the end of the existing Data. \\ENGLISH ENglish ON/OFF Switches all Reports from the Program (only with Terminal (^SCC.EXE^) between German and English Languages. The Program ^PARA.EXE^, ^L2.EXE^ and ^OFF.COM^ are not affected by this setting, but are always in German, these Output are relatively meaningless and for non German-Speakers of no consequence. \\ERASE ERASE <^BOARD^> <^Range^> The ERASE-Command erases the given Communications, in so far as the User of this Command, has the authority to use it. As a rule it is only permitted to Erase Communications, if the Person erasing is either the Author or the Addressee of the Communication(s). The Mailbox-Sysop may naturally erase any Communication. Die Box denies the Erasure always then, if the ability to erase, lies with another User. With DieBox-Systems the ERASE-Command will be given further to all other Systems. Only with DXL-Boxes: The Command will be employed on a self Authored Communication, if one has the Authority to edit the Header of this Communication (Receiver Call Sign, End-Mailbox, Subject) or to erase the complete Communication. The ERASE- Command can be shortened to the letter 'E'. \\EXITLOG :EXITLOG ON/OFF Decides, whether the Log is to be written immediately, (OFF) or whether it should wait until the Exit from the Terminal (ALT-X) is complete (ON) and then write to the Disk. Normally the Log Book is not corrupted, but it is possible, especially when using Laptops without a Hard Disk for it to be somewhat onerous. The disadvantage of the Intermediate Storage (RAM) is of course, that RAM working space will be occupied, and that with a Cold Re-start (Computer switched off or Crash) the recent Log-Data will be lost. Otherwise (OFF) the Data for the Log Entries will be produced and immediately written to the H-Disk/Diskette. With ON it is possible for the later Log Entry of Data to be falsely entered, e.g. if it is written for the first time on the following day. Cross Reference: ^LOG^ \\FILES L2.EXE - Is the actual TNC. Here is to be found in L2.EXE the Complete SCC-Service COMx-Software, and the AX25-Outlet. A part of the Command-Processor is also contained here. For all other Program Parts prior Installation of L2.EXE is necessary, the others are appropriately described elsewhere. Layer 2 is addressed with INT 47h, the recognition of its presence lies at INT 49h. SCC.EXE - The Terminal. A User Interface, which is required by L2.EXE for the PR Operation. Only the Terminal Functions are contained in SCC.EXE. The Program uses L2 as a TNC, whereby the Port is defined very closely to the machine and on this account not able to be used otherwise. PARA.EXE- A Parameter-Compiler, which creates SCC.PAR from the Text file SCC.INI and also for the preparation of TERMHELP.SCC for use by the Terminal. (PARA -H) OFF.COM - The 'Clear out Service'. Removes L2.EXE from the RAM, and resets the Interrupt Vector and saves, if the necessity arises Parameters altered from the Terminal in SCC.PAR. SCC.INI - The User-Parameter-File. All the important Command Parameters will be entered and contained here. The File is later clarified and then converted into the Form of Machine Readable Data in SCC.PAR by PARA.EXE. It is recommended that the File is examined and altered as necessary with an Editor, to undertake adaptations to the Personal Parameters as required. SCC.PWD - ^PASSWORD^-File. Is used for the Authorisation of Entry to one's own Station or for SYSOPs of ^TheNet^ or ^BayComNode^-Digipeaters. TERMHELP.SCC - This is the Help text, in which is contained all of the Program Help Assistance that can be requested. Is able to be extended by the user. SCC.VID - In this File, the Screen Contents are saved by SCC.EXE to be restored with a re-start of SCC.EXE. SCC.PAR - Will be produced by PARA.EXE and stores Parameters created in SCC.INI or altered from the Terminal. \\FIND ╔══════════════════════════════════╗ FIND <call> ║ Command for ^BayComNode^ & ^FlexNet^ ║ ╚══════════════════════════════════╝ With ^BayComNode^ this Command employs ^MHEARD^ in the search for a Station. The FIND-Command is only Compatible to ^FlexNet^. With FlexNet this Command has a more important meaning. With it, it is able to search for explicit Stations. From the Command the Digipeater sends to all of it's immediate neighbours, an ^UNPROTO^-Packet, in which the Station sought will be requested. An answer will be recorded if appropriate. The number of the Digipeaters, over which the information will be sought, is able to be determined by the Sysop. \\FlexNet Network Software from Gunter Jost, DK7WJ. Runs on a special Computer (^RMNC^), which has been developed in the Frankfurt area. FlexNet distinguishes itself by the fact that the Connection to the target is able to be constructed as via a completely normal ^Digipeater^, therefore one must not connect to the Node. From the time point of view, the accomplishment of the Connection will be a ^Hop-to-Hop^-Digipeating operation, i.e. that every Digi in the Chain immediately acknowledges a received Packet and then sends on to the next Digi. What it accomplishes itself, is through flowing running Connection outlets. A CallSign from FlexNet is, from now on available to an Autorouter. i.e. the Node always knows, to a greater extent, the accessible routes with the theoretical most favourable runtime. Consequently this ^Autorout^er has also been taken over in the ^BayCom^-Nodes. Additional qualities such as ^Converse^-Modes and the location of existing Stations, now from the user entry via a neighbouring Digipeater completes the FlexNet-Software. Commands of the FlexNet-Digipeater: (A)ktuell Issues latest Communication Text (B)eacon Outputs which Beacons are active (C)convers Switch on ^Converse^-Mode (C)onnect Connection Construction see ^Connect^ (D)estinations Shows known Digis in the Network (^Nodes^) (F)ind <call> Searches in the area for a User <Call> (I)nfo Outputs Info-Text about the Digi (L)inks Output of the Link partner, see ^NODELINKS^ (Q)uit Severs the Connection to the Digi (S)etsearch Outputs Digis, which will operate with ^FIND^ (U)sers User List, see ^NODECSTAT^ \\FORWARD Automatic onward transmission of Information to other ^Mailbox^es. There is a difference between the forwarding of personal Communication and that of General Communication. With personal Information, the explicit delivery Mailbox of the Addressee must be given after @ in the ^Send^-Command (see ^DieBox^, ^DXL-Box^) The Information given will be forwarded to the BBS of the Addressee over the PR-Net. The possible Mailbox calls are obtained from the lists circulated from time to time. Warning: Forwarding to most of non European: Continent/Country Designator must be given, for correct forwarding to the desired recipient.(to USA and State). General Information: a ^Distrib^utor board will be given from which the Information will be distributed to all Mailboxes (where it lands, from time to time in the appropriate Boards). \\FRACK :FRack <100ms-Value> (=Timer 1). Indicates a Start Value for the point of time for the Repeat of a Frame, if no acknowledgement has arrived. The true Timer 1 adapts itself during the Connection according to the through put answer time of the Partner. (round trip timer). The Time will be given in 100ms-Units. Valid Values lie between 40..60 With ^HBAUD^ 300 Frack is automatically not active, which in operation on H F has been shown to be undesirable. \\FREE ╔══════════════════╗ FREE ║ Only for ^DXL-Box^ ║ ╚══════════════════╝ The Command outputs the RAM Space, which the Box has still available Communications. Short Form: F. \\GATE ╔════════════════════════╗ GATE ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ switches on the ^DXL-Gate^way. If the OE5DXL-Software is not installed, an Error Message is given. \\GATEWAY ╔══════════════════╗ GATEWAY ║ Only for ^DXL-Box^ ║ ╚══════════════════╝ switches in the Node-Part of the Digipeater (on Original-DXL- Systems the so called Gate). \\GERMAN GERman ON/OFF Toggles the German Umlaut from IBM-Character Set which, on Packet-Radio is mostly the DIN-Character Set. The outcome of this change is that no square brackets [] and arched braces {} will be transmitted. GERMAN ON : DIN-Character Set [\]{|} will NOT be displayed GERMAN OFF : IBM-Character Set, all Characters as original Consequently consideration must be given to ^WRITE^ and ^READ^. With a live Connection (and only then) a change with ALT-U between DIN and IBM is possible. Displayed in Upper ^Statusline^ at the right hand side. As soon as a received Character indicating that the QSO-Partner is able to send/receive IBM-Characters, the U flashes in the StatusLine, to indicate a possible incompatibility. \\HARDWARE ╔════════════════════════╗ HARDWARE ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ Issues a Description of the Digipeater-Hardware (if loaded) \\HBAUD HBaud <Channel> <Baudrate> Operation with ^SCC-Card^: The Baudrate is able to be set quasi stepless. A Quantification generally follows in Fractions of 38400. With a Hardware Clock (see ^CARRIER^) HBAUD is only effective for the receiver. COM1/COM2: Only 2 Baudrates are able to be set: HB 1200 and HB 300 All others are meaningless. A Stepless Value is unfortunately not possible. !!! After the Alteration of the Baudrate at least one Packet !!! must be sent before the change is usable. \\HDLC HDLC = High Level Data Link Control This abbreviation describes a Procedure, that will be employed for the Error Protection of Packet Data transmission. The procedure and the coding is described in the Norms ISO3309 and ISO7809 and is able to be used directly for the fundamentals. In the AX.25-Protocol a Modification of HDLC will be used. \\HELP :HELP <Key Word> gives Help for the Key Word CTRL-F1 Help for the Word under the Cursor or stands one place to the left of it. ALT-F1 Repeats the previous active Help text. Additional Help for:- ^Screen^, ^Keys^ and ^Modem^ ^Term-Comm^ands, ^TNC-Comman^ds, ^INI-Comman^ds In the Help Window the Key Functions are: Z (AltF1) back I Index (= Key Word list) E (ESC) Close Help Window H This page Screen Pages in Multi-page Texts PgDn/PgUp (Ind. Lower Right) \\HENNING :HENning <Channel><0 / 1> Switches on the homing of the 9600Bd-Modem from DF9IC, which requires NRZ at first instead of ^NRZI^ Coding, and to the other prescribed external RX and TX-Time. The Name of this Command comes from the name of the Modem developer: Henning Rech DF9IC. The Modem with others is contained on the BayCom-USCC-Card. It operates as a further development of the Modem from James Miller, G3RUH. On the USCC-CARD this Modem is Connected to Channel 3, it is therefore at all times to be set: HENning 3 1. \\Hop-to-Hop Under 'Hop-to-hop-Acknowledge' it is understood that it has the ability of a ^Digipeater^, and via it's running Data intermediate storage to enable damaged Data to be repeated again from itself. At the beginning of the Packet-Radio-Era it was usual for Stations to be employed as Digipeaters, with each single Packet being carried over, without itself having any concern about the pre-History or the future of the Packet. That has the consequence, that damage to a Packet on a long stretch will only be able to be adjusted from the first and last Station, and to be sure at times via the whole route. In between are all 'singing and dancing' NetNodes in a position to manage self Connection and eventually to execute mature repeats of Packets on shorter routes. \\INFO :Info Sends Information Text about the Station. This Text must have the File name INFO.SCC and be saved on the H-Disk/Diskette. This Command should be used for assisting unfortunate non-users of BayCom in the art of enjoying your Station in addition to any Information you wish to impart. Remote usage: //INFO. \\INI-COMMAN Commands, ONLY allowed IN the Initialisation File ^SCC.INI^: ^BLINK^ Flashing in the upper right Corner, when L2 runs ^BUFFER^ Quantity of RAM blocks, to be reserved for L2 ^COMBASE^ Basic Address of the Employed COM-Port ^COMINT^ Interrupt Number of the COM-Port ^D1LINES^ Number of Lines in the TX Window (1. Statusline) ^D2LINES^ Number of Lines in the RX-Window (2. Statusline) ^DOSCLEAR^ Screen Clear at the Program end ^INSMODE^ Insert-Mode setting at the Program Start ^RBUFFER^ Quantity of Blocks in the RX Buffer ^RS232^ Number of the COM port for PR operation ^SCCBASE^ Basic Address of the SCC-CARD (If Fitted) ^SCCINT^ Interrupt Number of the SCC-CARD ^TBUFFER^ Quantity of Blocks in the TX Buffer ^VADAPTER^ Type of Video Adapter ^VCOLUMNS^ Number of Characters per Line ^VLINES^ Number of Lines per Screen ^WWRAP^ Position of the Line Feed ^MOUSE^ Switches the Check for Mouse Driver To Observe in addition are: ^TNC-Comman^ds and ^Term-Comm^ands! \\INIWRITE WRITE The opening of Files now is able to be included in the SCC.INI File. The eventually open File(s) will be saved at the end of the Program. Then at the next start of the Program it/they will be restored to the previous state, when it had been saved. What is more, by this method it is able to exit the Terminal, whether Binary File Transfers are being sent or received, in order to undertake another task in the meantime. Then of course only as much will be sent as is remaining in the Buffer. This results in no Error, it will then be switched OFF by L2. Note: This does not mean an exit from the Terminal using a Batch File that contains OFF.COM. \\INSMODE :INSMODE ON/OFF Decides, whether the Terminal starts in the Insert Mode, when a key that is pressed inserts its Character at the position of the Cursor (ON), or in the Overwrite Mode when a key pressed overwrites the Character at the Cursor Position (OFF). The Mode is able to be toggled with the INS Key. \\IPOLL :IPoll <decimal> Maximum Info-Length, which will be requested with I-Poll if an Acknowledgement is outstanding. A Length of a maximum of 80 (approx.) Characters is reasonable. With this value the statistical Barrier lies between Total Overhead and Profitable Data. \\KANAL ╔══════════════════════════╗ :Kanal <decimal> ║ Only Valid with ^SCC-Card^ ║ ╚══════════════════════════╝ SEE ^CHANNEL^ Through the preceding ^NRZI^-Coding and ^BITSTUFF^ing it is able to be determined from the number of received 1-Bits, whether it is handling valid Data or only noise. PgDn for explanation of Operation To decide whether the "Channel is Free" or "Channel Occupied", Variable X will be altered according to the following criteria. - more than 6 1-Bits: Data stream invalid or Frame Reject -->X:=0, DCD will be immediately switched to "Channel Free" - precisely 6 1-Bits: Flag, will be utilised for the Beginning and end limits of Frames and will be sent for the synchronisation at the Start. For such a Token to be received, X will be raised by 5. - Less than 6 1-Bits, it could be Valid Data being handled. X will be raised by 1. - X>=10 means:"Channel is Occupied", X<10 means: "Channel Free" \\KEYS ALT-X ends the Program, ALT-1 Cursor to the upper Window of the Screen (TX) ALT-2 Cursor to the middle Window of the Screen (RX) ALT-3 Cursor to the lower Window of the Screen (Monitor) F1 ... F6 Switches between the individual Ports. F9 Cursor moved to the next Screen Window F10 Monitor, Unproto. ESC or TAB: Switches Command-/Data Mode, colon Toggle SHIFT-TAB: Stops the output on the selected Port. CTRL-RETURN: Cursor to next Line, without executing the line PAGE-DOWN: Text scrolled one Page upwards PAGE-UP: Text scrolled one Page downwards CTRL-PAGE-UP: Mon. Window enlarged, Quantity of text increased CTRL-PAGE-DOWN: Mon. Window reduced, Quantity of Text decreased CTRL-HOME: TX Window reduced, Quantity of Text decreased CTRL-END: TX Window enlarged,Quantity of Text increased \\KNAX :KNax ON/OFF Toggles a 'Knack'-Noise ON or OFF, This is produced as each RX'd Line arrives at the Terminal. Through this 'Knaxen' it makes an awareness of the arrival of RX Data. Up to Version 1.2 this Function was permanently active. Sometimes this may affect the nerves, for that reason it is now switchable. Cross Reference: ^CBELL^ \\L2.EXE L2.EXE is the definitive TNC of BayCom. The Program will be started and runs from now on as a resident Program in the RAM. It behaves as a TNC, consequently it is able to be connected to, and save the Contents in the interim, between incoming Calls. However it is not possible to be Remote Controlled, so long as the Terminal ^SCC.EXE^ has not been started. The exiting of L2 is achieved with the Program ^OFF.COM^. \\L2CTEXT :L2ctext <text> This Text (Maximum 1 Line) will be sent to each Connectee when Operation is WITHOUT Terminal. (SCC.EXE) The L2CTEXT will be only sent, if the Terminal ^SCC.EXE^ has not been started, but only L2 running in the background. If the Terminal is running, only ^CTEXT^ will be sent. Cross Reference ^ANSWER^, ^QTEXT^ \\LIFETIME Lifetime (Life Duration) The Lifetime is the maximum Time Duration in Days from the Arrival of the Communication, after which in the pertinent ^BOARD^ will be automatically erased. It will be set for ^Bulletin^-^BOARD^s individually by the Mailbox-Sysop. For User-Boards there is a Standard-Lifetime, which most of the owners of the User-Boards are able to alter within a conscience limitation. \\LINK :LINk <call> <Kanal (channel)> Creation of a Link-Partner on a Selected SCC-Channel It is able to be defined previously for up to 8 Call Signs Thereby Kanal will be set on the required SCC-Channel With :LINK <call> ** the Call will be cleared from the List Example: link db0aab 0 link db0pv 1 Unconditionally with the attachment, it is able to select a particular Channel with :CONNECT Command. If no Channel has been given the Program orientates itself onto the Port that the Call last appeared in the MHEARD-List. \\LINKROUTER So called; which in the Gigahertz Range carry Connections between Digipeaters. The Link routes will be managed in part, with special Modems at higher Speeds (up to 9600Bd) and makes possible a rapid Data Transfer. Because the construction of such Routes are extremely expensive and also not technically simple, the number of Digipeater to Digipeater Linkroutes is very variable. \\LINKTIME :LINKTime <decimal> (CHECK, Inactive link timer, Timer 3) tests the Connection if there is no Data flowing. LINKTIME operates in 10sec-Units! If nothing is happening with the Connection, then after the Runout period of the Timer the following is sent:- RR,P . RR,F. This will establish, whether the Connected Partner is still there. If not, the Connection will be broken. \\LIST :LIST Shows all of the saved Standard Texts (see ^ST^) It is able to Edit by placing the Cursor in the Texts. :LIST A Lists only the Text with the Letter A \\LOG :LOG ON/OFF Toggles the automatic Log Book Update ON or OFF. The Log Entry will be made in the File LOG.SCC and is able to be read and edited with a normal Text Editor. New Entries will always be entered at the end of the existing entries. Cross Reference: ^EXITLOG^ \\LTASKS ╔════════════════════════╗ LTASKS ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ Lists the Status of the Process Administration. The output is only for Debugging purposes and in Practice is without meaning. Never the less it will be explained for those interested. Example: Task Stack Event Port Ticks Address 0 214 2 48 5548 3B0B:0004 1 312 1 49 26 3B0B:0331 * 2 86 0 45 1 3B0B:065E Wait: 1 0 Stack: 548 548 470 0 0 0 0 0 0 0 0 0 Task: Running Number of a Process Stack: Immediate Stack depth of a waiting Process Event: Event up to which Entry the Process is suspended 0 Process runs forward 1 waiting for free Send Buffer 2 waiting for received Data 3 waiting for Connection Construction 4 waiting for DOS-Access 5 waiting for Characters in the Monitor Buffer 6 next Time slot awaited Port: Port number of the Layer 2, with which this Process corresponds Ticks: Used up Time 13ms-Units since Suspension Address: Far Pointer on the den Task-Control block Wait: Wait slot for the continuation of the waiting Processes Stack: Maximum obtained Stack Depth of all Task-Blocks \\MAIL ╔════════════════════════╗ MAIL ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ Switches to the next located Mailbox. If a Mailbox is installed in the System, then this one will be called. Otherwise the next appropriate Mailbox over the Interlink will be called. If there is no Box configured, the Connection Construction will not be made. \\MAILBOX Mailbox System A Mailbox allows the Receiving and Sending of Information to a particular User (personal message) and to ALL - (^Bulletin^s). Mailboxes exchange Information between themselves in the Store-and-^Forward^-Process (S&F). There are various Mailbox Systems, which all offer similar Store Functions (Reading and distribution of Information, Participation in Forwarding Traffic), however they themselves, differ in the exact handling of the Commands and the offer of supplementary Functions. In the German Language Mailbox Systems, at the present two are distributed substantially. - - ^DieBox^-System - ^DXL-Box^-System Stored Radio Amateur Information Traffic lies in the limited ^Contents^ of the Mailboxes \\MANUALS The Manuals Comprise the following- SOFTWARE, RS232 Standard Modem, RS232 SMD Modem, USCC-Card All four are available in the German Language. Only the Software Manual has been translated into English at this time. The remainder will be completed shortly. \\MAXFRAME :MAxframe <Channel> <Quantity> Maximum Quantity of Packets, which will be sent in sequence, before an Acknowledgement will be awaited. Valid Values are in the range 1 .. 7, other installed Values can lead to highly Individual Effects. !! The adjunct <channel> is only required when an ^SCC-Card^ is installed and in use. \\MBUFFER MBuffer <Quantity> The Quantity of the ^Buffer^-Blocks, which will be used for the intermediate storage of the ^Monitor^ Data. If the Terminal ^SCC.EXE^ is not in operation, the received Data will be stored temporarily. The amount of this Data is dependent on this Parameter. All additional incoming Packets for the Monitor Display will be thrown away. An overrun (which with TNCs is allowed) will not occur. The Quantity of the Buffer Storage is indicated in 330 Bytes (this devious Value is decided by the maximum length of a Packet) and should be set at a maximum of HALF the value of ^BUFFER^ Blocks. For Net Node Operation MBUFFER 2 should be installed. \\MCALLS :MCalls <call1> <call2> .... Sets the Selected Call Signs for Monitoring Purposes. It is possible to set a maximum of 8 Call Signs, which are dependent upon the setting of ^MSELECT^ in order to be taken into account. It will exploit either single or pairs of Call Signs. If no ^SSID^ is given:- then the Calls under all SSIDs will be valid. \\MHEADER MHEADer ON/OFF switches the output of the Monitor-Address same/separate Line. With MHEADER OFF each Packet displayed on the Monitor will be written on the same Line. MHEADER ON gives a Line Feed between Address and Information field. \\MHEARD :MHeard issues Call Signs that have been heard MH Shows the directly heard immediate Call Signs MH * All Call Signs that have been heard during the last 120 min, without Path. MH # All Entries during the past 15 Minutes, with Path MH <call> Time, Path and ^SSID^s, if the <call> has been heard By including Px it is able to select a Modem Channel, in the case where more Modems are in operation (e.g. MH P2 #). P0 indicates the first Channel. If a Time (in Minutes) is given, then an output follows from this time, e.g. MH P2 * 20 -> all Entries during the last 20 minutes on Channel 2. Times will be given in HH:MM. The Time that is shown is the time that has past since the last Packet was monitored from that Station. (Therefore not the Clock time!) \\MODEM Information for Connections (WARNING: beware of unusual configs.) Signal 25pol 9pol Description ----------------------------------------------------------------- DTR - 20 - 4 - Send data +-10V RTS - 4 - 7 - PTT Hi-active, therefore -10V=RX, +10V=TX CTS - 5 - 8 - RX-Data. Mostly correct TTL-Level GND - 7 - 5 - Ground TXD - 2 - 3 - Unused, (Timing Outlet) ------------------------------------------------------------------- For the Connections DTR, RTS, TXD via 3 Diodes the Voltages are able to be obtained and used without Modem Current Problems. This is of course a parasitic method, in the event of an overloaded Serial Port Driver no responsibility will be accepted !!! \\MONITOR :MOnitor <Channels> The actual Modem-Channels, which will be displayed on the Monitor. MO 0 1 2 3 4 5 6 7 allows these Channels to be displayed, MO 0 for example, displays only the first Channel. This option is only relevant, when more than one Modem is being employed. With the use of single Channel on COM1/COM2 only MONITOR 0 is valid. To completely switch the Monitor off, an unusable Channel No. should be issued, e.g. :MO 9. !!! From Version 1.50 the Parameter must have spaces between each !!! Channel Number. \\MOUSE ╔═══════════════════════╗ MOUSE ON/OFF ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ With this Command it is able to be directed to search for a Mouse Driver. Normally this Command is always ON, in the absence of a Mouse Driver, it will discover this automatically, and the Mouse will remain inactive. There are two reasons when it is desirable for this Command to be OFF: *** There is no Mouse Driver on hand, and the employed Interrupt Vector INT 33H is undefined. Example : branches to an ERROR (Possible to occur with very old PCs) *** There is a Mouse Driver there, but it is not wanted, e.g. because it considerably slows up the Program Start or because the Mouse Cursor is causing a disturbance. \\MSELECT :MSelect <decimal> The actual Monitor-Select Mode. With which the individual Calls are able to be selected: using the following Values. 0 Monitor-Selection off, i.e. displays all received Calls 1 QSO-With cut. The ^MCALLS^-Call Signs will be evaluated for stable pairs and only Connections, in which BOTH Calls Signs are present will be displayed on the Monitor. It is possible for more pairs to be displayed simultaneously. 2 MFROM Only Packets FROM the Call Signs in the MCALLS-List will be displayed on the Monitor. 3 MTO Displays only Packets TO the ^MCALLS^-Callsigns. +10 With 10 added (11,12,13), then the corresponding Function will be inverted, i.e. the selected Calls will NOT be displayed, otherwise completely normal. \\MSG ╔════════════════════════╗ MSG ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ With this Command it is able to enter the Converse Mode. Possible applications are: msg <call> ..text... ;Text sent to the Station <call> msg <call> (without Text) ;everything sent to <call> msg <number> ;switches on Converse Mode <number> See also ^NODECONV^ \\MYBBS MYBBS <Endmailbox> All Communications addressed to the individual Call Sign will be forwarded immediately to the designated Mailbox in the MYBBS-Command (^S&F^). This Information will be forwarded to all other DieBox-Systems, so that one must only make the Output to one Box of the DieBox-Systems. DXL-Boxes do not support the forwarding. \\MYCALL :MYcall <call> [ <call> .... ] One's own Call Signs. Entries of up to 4 MYCALLs area able to be included. These are the Call Signs by which the Station is capable of accepting Connect Requests. Outgoing Connections with the ^CONNECT^-Command:- the first call from the list will be persistently employed. It is necessary for the Operation of Packet-Radio to enter here, the individual Call Sign. It suffices of course for a declaration of a single Call Sign, it is however not possible to enter more than 4 Call Signs. \\NAME ╔═════════════════╗ NAME <Name> ║ Only for ^DieBox^ ║ ╚═════════════════╝ With this Command a Forename is made known to the Box. After which, a greeting with this name will be issued at each Log in. \\NETNODE NetNodes are Stations, which are in the locality to forward Information via a Data Net. This outlines each variation of a Packet-Radio-Station. In general Nodes are compact, unmanned, installed Stations (^Digipeater^, 'Network-Node') sustaining Radio Links to other Nodes and for the End-User ('Terminal-Node') giving access to the selected other places. This System is able to find other NetNodes automatically, and in part, (see ^FlexNet^), other individual Systems which are to follow in the Locality, ^User-Routing^ (BayCom, DXL). ^BayCom^ offers a Terminal-Version, which is thought of as the tool for the End-User, and a Node-Version a tool for the Digipeaters. Certain Commands in the List are relevant only for the Node-Version. Other common Node concepts are for example ^FlexNet^, ^TheNet^, ^DXL-Gate^ \\NODE Nodes are Stations, which are in the locality, to forward Information via a Data Net. This outlines each variation of a Packet-Radio-Station. In general Nodes are compact, unmanned, installed Stations (^Digipeater^, 'Network-Node'), sustaining Radio Links to other Nodes and for the End-User ('Terminal-Node') giving access to the other selected places. ^BayCom^ offers a Terminal-Version, which is thought of as the tool for the End User; and a Node-Version, a tool for the Digipeaters. Certain Commands in List are relevant only for the Node-Version. Other common Node concept are for example: ^FlexNet^, ^TheNet^, ^DXL-Gate^ \\NODES ╔══════════════════════╗ NODES ║ ^BayComNode^ Command ║ ╚══════════════════════╝ Outputs the NetNodes known to the System (NODES as ^DESTINAT^) The List will be held compatible with the established running ^FlexNet^-Router. It is also able to extract from it, that the presented Stations are also actually attainable. Entries, for which the Router refers back, are those for which therefore must have a Link-Loop built, will NOT be displayed in the List. N * Lists all Entries, accordingly the previous and which, are not immediately accessible. N LOCAL Lists only Nodes which, are accessible with a Run Time under 100sec. N <call> Shows the Path to <call> (see also HELP ^PATH^) \\NODECONV In ^Converse^-Mode all usual ^NetNode^s become available with the Command CONV. With ^BayComNode^ the following Commands function: /users lists present Users of the Converse Mode with Channel No. - means, that the User not in Converse Mode, but is logged into the Node, is able to be addressed by Call Sign. /quit Exit Converse Mode. /<x> Change to Net <x>. (e.g. /25) /<call> Set down Info to a <call>. (e.g. /dk5rq) - Consequently other customary Commands /who /bye /exit / channel /msg /write functions are permitted in the Corresponding Places. - with /<call> or /<x> the End Group will be changed. Giving a Message (e.g. /dg3rbu this is a Test), only this will be sent, the immediate Mode remains held. - Installed Commands (e.g. /u) will be able to be given therefore without / , single Letters will not be sent onward. \\NODECSTAT ╔════════════════════════╗ CSTATUS ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ User-Lists similar to RMNC/FlexNet. A Channel number will be given, (e.g. cs 5) so, only the Links from this Channel will be given. The List shows first of all, the Calls, which are connected with the Node, and there under (by Empty Lines severed) the Calls, which are connected via the Node. The List is sorted by Channel number. 37: S5 U2 P3 DB0RGB>DL8MBT v DB0LNA* DB0AAB* | Digi chain | Sender- and Target Call Sign on this Link | Number of un-Acknowledged Frames on this Link | Link Status (1=disc 2=link-setup 3=disc-request 4=FRMR 5=info-transfer 6=wait-Ack 7=REJ-sent) | internal Port number \\NODELINKS Here the neighbouring Digipeaters will be shown. The Call Sign displayed will be routed out on the corresponding Channel If no ^SSID^ is given, 0-15 is valid on this Link, with an explicit declaration of only one SSID The Call Sign will be given, whose Reply Time is in 1/10sec Units and the SCC-Channel number, therefore the Radio Route. PgDn for an Example: M.NORD:DB0AAB> Links: Call-------Time/Rev----via OE7XAR-2 29 P1 DB0LNA 52/49 P2 DB0PV-6 3 P3 DB0MWE --- P4 DB0KFB 83/94 P5 DB0EIC 36/40 P6 DB0APW ( 257/329 ) DB0PV-5 DB0PV-0 25 DB0PV-15 - The simple numbers enter themselves onto Neighbours, which do not dominate the ^FlexNet^-Routing Protocol. Here the Link will only be submitted with the following SABM -- UA getestet, which is relatively inaccurate. - The doubled values (divided by / ) cover themselves on FlexNet-Compatible Neighbours. With these the Link Routes will be measured with a 240 Byte long Test frame. The two numbers cover themselves by Out and Return ways. ----means, that the Link at the moment does not function. - Values in Brackets mean, that the System knows a better Route, than the direct one. Consequently it will measure to be sure, but not used immediately from the Router. \\NODEUSERS ╔═══════════════════════╗ ║Command for ^BayComNode^ ║ ╚═══════════════════════╝ USERS shows the List of all immediate Users. 'Mailbox' The List shows in the first place, those Call Signs that connected with DXL-Software. By the side of which will be given in Brackets the Call Signs, under which the connection is running. Consequently Downlink-Ports will be given, as long as the Connection is not yet established. The Call Sign is in Brackets under, which the connection is being constructed. 'Update' The Link Data-Exchange with other Digipeaters. 'Node' The following Entries, which are connected with BayCom-Node, and have not constructed a Downlink. 'Circuit' Finally the switched Connection will be output, whereby will be enabled (in so far as it is able to be established) Upward- and Downward Digis. The manner of output is either by Call or Symbolic, and afterwards how the Connection has been constructed. 'L.setup' signifies, that a Connection 'via' the Node will be constructed immediately, but the DownLink-Partner has not yet responded. u <channel> produces how, Call Sign <channel>, a Radio Channel only will be listed. See ^NODECSTAT^ \\NRZI NRZI (Non Return to Zero Inverted) This Coding will be used for the Transference of Packet Radio Signals. It operates on the premise, Data Direction will always be sent as a 0-Bit always meaning a Change of Direction and a 1-Bit as "No-Change". With this Coding the Polarity is unimportant and many inverted constituents are able to be switched optionally. In addition it allows itself improved quality of the Self Timing by ^Bitstuff^ing. \\OFF.COM OFF.COM A Program to remove the resident ^L2.EXE^ from the RAM. OFF ? requests the State of L2 in Use or not. With L2 removed by OFF.COM, all Interrupt Vectors and all occupied RAM will be freed and returned to normal. If after the Start of ^L2.EXE^ further resident Programs are to be installed (e.g. such as Norton Commander or others), then immediately after it's End, the vacated RAM will be usable once again. The 'RAM Slice' will not be managed tidily under DOS. \\OSHELL :Oshell <DOS-Command> The Shell to DOS-Command. The COMMAND.COM will be loaded and the Screen will be changed to the normal DOS-Screen Display. The Remote Control of this Command is also possible but VERY UNDESIRABLE FOR HARD DISK USERS. It should be barred by correct use of ^RCMD^to avoid your Hard Disk being :- Wiped, Re-Formatted or Infected with a Virus by an unscrupulous User. !!!!!!!!!!!!! Of course the amount of RAM that is available for the SHELL to DOS is not very large, therefore only very compact operations may be started with this facility. But for the simple things such as DIR, DEL and COPY it will give no problems. \\PACLEN :PAClen <decimal> PACLEN, maximum Frame length, valid for the User Interface (SCC.EXE), for Interlink-Connection (e.g. Digipeating) the original-Frame length of the input will be output. !!!! WARNING: 0 is not 256, but 0 (leads to a Crash !!) PACLEN 256 is a valid Value, above that Special Effects are likely to occur !!! \\PARA.EXE PARA.EXE A Program, which converts the Parameters in the Text File ^SCC.INI^ into a Machine Readable Format prepared for the use of ^L2.EXE^. If ^SCC.INI^ is altered, an automatic PARA- Call follows at the next Start of ^L2.EXE^. A further facility of PARA.EXE is, that it is used for the Compilation of the Help File ^TERMHELP^.SCC. If the Help File has been edited, it is then necessary to re-Index and Check by the Command: para -h An altered, non updated Index Help File is not serviceable, :- the alterations will not be accessible. \\PARMS ╔═══════════════════════╗ PARMS ║Command for ^BayComNode^ ║ ╚═══════════════════════╝ PARms Output of the installed Parameters PAR shows all Parameters PAR 1 only Layer 1 Parameters PAR 2 only Layer 2 Parameters PAR C Notification of the available Call Signs PAR M Output of RAM- and Port No. \\PASSWORD The Password-Generation follows fully automatically for DXL-Box and ^BaycomNode^ as soon as 'pw' is issued. Now the BayCom Terminal also makes full use a of Password, it is able to be demanded with //j. It then opens the entire Remote Control possibilities, if it is correctly answered. The production of the Password resembles the Netrom-Gepflogenheiten. (Practice) In the File ^SCC.PWD^ an 80 position String is able to be saved, in which each Position will be associated with a Number and thus is able to be checked for an Agreement. \\PATH ╔═══════════════════════╗ Path <call> ║Command for ^BayComNode^ ║ ╚═══════════════════════╝ Shows the route to <call> (if known to the System). The Path will be taken first from the Node-Lists. If there is no Entry there, then the MH-Lists will be searched. The Call is able to be reconstructed from the relationship between Node- and MH- Lists, in this way it will be output. At first the Route will be output only so far as, how the System is directly acquainted Additionally a Packet will be sent on the Net, which pursues the entire Path over the Autorouter and with the return, displays the complete Path. This second exercise however takes a long while, because substantially all intermediate Nodes will be interrogated. \\PRINTER :Write PRN Switches on the Printer. Which will, as under MS-DOS, handle all implementations for Files, it is possible by using DOS Protocol, to use every Output variation. For this reason there is no single Command for Printer Operation. Thus, it gives the greatest possible flexibility of usage. A Special significant application is also available by use of :Write NUL Whereby Mailbox Contents of the usual indescribable significance is able to be secured. That saves Paper and it gives guarantees that no important Information will be lost. :Write OFF Switches the Printer Off Line \\QTEXT :QText <letter> This Parameter recognises a Standard Text (^ST^), and which will be sent either with the issue of ^QUIT^ from the Terminal or //QUIT from the QSO-Partner. Here it is able, to send more or less interesting 'Floskeln' than 'auf Wiederschreiben' ('til we write again). Or perhaps, something that is perceived to be a little less courteous. !!! Cross Reference: ^L2CTEXT^, ^CTEXT^, ^ANSWER^ \\QTH ╔══════════════════╗ QTH ║ Only for ^DXL-Box^ ║ ╚══════════════════╝ An in the Box integrated Program for the calculation of the Distance to the Box out of the Output of the individual QTH-Connoisseur. \\QUIT QUIT Severs an established Connection, the same as ^DISCONNECT^. In order to ensure that all Data has arrived from the Partner, it will wait for the remaining outstanding Data to be acknowledged. Before the Disconnection ^QTEXT^ will be sent. If the case is hopeless, so to speak, such that the Data does not arrive, ^TQUIT^ will be awaited and then the Connection severed. This Command is especially valid for Remote Control in the Form //QUIT because then both are able to be certain, that Data has arrived. \\RANGE ╔═════════════════════════════════════╗ RANGE ║ Only For ^DieBox^ and ^DXL-Box^ Systems ║ ╚═════════════════════════════════════╝ The Output Range is in both ^DieBox^ and also in ^DXL-Box^- Systems and is always available where a Quantity of Information is able to be selected (e.g. with the Command LIST, ^READ^ and ^ERASE^). An Output Range must precede a ^Board^name, if it fails, use the DXL-System, which ultimately will have been addressed. The Range Output selects from this Board actual Information, for which the issued Command requested. The request of the Information follows from the Output of the Info-Numbers, which the ^Box-LIST^-Command (DXL-Box: ^DIR^) shows. From that the following alternatives exist: Range Output ! the selected Communication --------------+---------------------------------------------- <no> ! DXL: all Communications of the active ^Board^s 5 ! only Communication No. 5 -7 ! the Communications 1 to 7 3- ! all Communications on the Board from the third 2-5 ! the Communications 2, 3, 4 und 5 Example for Commands with Range Output: r satellites 1-4 read Communications 1 to 4 of the Board's "Satellites" d info -10 shows the Index Contents of the Board's "info" to the no 10 Communications e dx 4 erases the fourth Communication of the Boards DX \\RBUFFER RBuffer <Quantity> The total Quantity of ^Buffer^-Blocks of RX Data which will be stored temporarily. If the Terminal ^SCC.EXE^ is not in operation, the received RX Data will be stored temporarily. How much is possible per Port will be decided by this Parameter. The Quantity of Buffer Storage is indicated in units of 330 Bytes. (this devious Value is derived from the maximum length of a Packet) and should be set to lie at a minimum of 7. \\RCMD :RCMD <Commands> Gives specified Commands freed for Remote Control. Remote Commands will be compared against this List before allowing execution. Abbreviation is possible for all Commands. Example: :rcmd cstatus info mheard quit users help opens the Remote Control, also for the shortened //cs or //q. :rcmd * ; allows all Commands for Remote Control. Advice: Please no Complaints, that the Number of Commands do not suffice. BayCom is a Terminal, not a MailBox, and the Remote Control has a consumate subordinated Roll here! \\READ :Read <filename> Reads a Text File from the Disk (including Path <File name> if required) and sends it out as Text to the Partner. Also, the customary DOS CR LF Carriage Return which in Packet-Radio is normally CR only, will be converted. Additionally with ^GERMAN^ ON the German Umlaut will be converted to the DIN-Character Set, this must be heeded by users of the German Language only. \\REMOTE REMote ON/OFF This Command decides, whether the Station is able to obey Remote Commands or not. The Remote Commands must be given in the Form //Command and are able to be selected by ^RCMD^-Function. With the use of the ^Password^ it is possible to enable a complete Remote Control of the Station. \\REPLY ╔══════════════════╗ REPLY ║ Only for ^DXL-Box^ ║ ╚══════════════════╝ This Command given immediately after the Reading of a Personal Message, makes available the ability to immediately send an Answer to this Communication (without an extra ^SEND^-Command required). The Sender of the originating Communication will be set as the Receiver, End Mailbox is the same Box, from which the Communication has been sent. The originating reference will be an RE: set before it, in order that the Communication will be recognised as an answer. The abbreviation for this Command is REP. The issue of the Communication follows as described for the ^SEND^-Command. \\RESPTIME :RESptime <100ms-Units> This Value must be different to Null, but is not actually needed. With bilateral Data flow, the Acknowledgments are able to be of one's own free will, if T2 has a value that is greater than ^DWAIT^ Consequently in practice a setting of RESPTIME 2 (approx) is reasonable, other Packets are able to arrive resulting from short Pulse gaps, in which more words arrive. \\RETRY :RETry <decimal> The Maximum Number of Retries. With SABM and DISC without a Digi the Value RETRY/2 will be employed in order to avoid an unnecessarily long Waiting Times if a Station is not available. \\RMNC Computer System, containing more Channel Cards with Motorola 6809-Processor and Z8530-^HDLC^-Controller. Developed by the Frankfurt PR-Group, this Computer System with the accompanying Software ^FlexNet^ is found to be expanding rapidly in the whole European Area. \\RPRG :RPrg <filename> Reads a binary File from the Disk and transmits it. The Data will be sent transparent, however it follows that there will be no recognition of the beginning or end of the File which, must actioned by the user. i.e. <CR> at the end and before :- Automatic Binary file transfer is not implemented. \\RS232 ╔═══════════════════════╗ RS232 <COM Number> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ In ^SCC.INI^ the Port on which Packet-Radio will be operated (COM1 or COM2) will be given. The use of COM3 and COM4 is only possible in limited circumstances. See ^COMINT^ and ^COMBASE^. If an ^SCC-Card^ is employed, 0 is the Value to be installed, it should allow the RS232 to be able to be used additionally for an additional Channel. In practice this is quite possible but mostly not significant/sensible. \\S&F Short for 'Store and ^Forward^', (Speichern und Weiterleiten.) Behind these words is concealed the ability of the ^Mailbox^es, to accept Information from Users and to hold it, then at a suitable time send it to the given End Address. \\SATTRIB SAttrib <Window> <hex> Selects the Screen attribute for the Screen Window <Window> 0 TX-Window 1 upper Status line (Between RX-TX Windows) 2 STOP-Character (In Upper Status Line) 3 RX-Window 4 Lower Status Line (Shows Call Sign and Port No. of Connect) 5 Lower Status Line (Not Selected and no Connect) 6 Lower Status Line (Selected Port) 7 Monitor (Address Field) 8 Monitor (Info field) 9 Help Text 10 Help Text (Marked Text that can be selected) 11 Help Text (Selected place by the Cursor) 12 Control-Character (Must be different to 0,3,7,8) Hex-Numbers of the Colour attribute: 0=Black 1=Blue 2=Green 3=Cyan 4=Red 5=Magenta 6=Brown 7=White 8=Dark Grey 9=Light Blue A=Light Green B=Light-Cyan C=Light Red D=Light Mag E=Yellow F=Light White Example: :SAttrib 3 1E RX Output: yellow writing on a blue Ground \\SAVEPORTS :Saveports <decimal> Gives the Number of Screens, which will be saved to Disk at the end of the Program. It is advisable that when using a slow Computer or Diskettes, that only one Port be saved or the Function completely switched off by :SAVE 0. \\SCC-Card BayCom-SCC-Expansion Card for IBM-PCs ------------------------------------ This Card has been developed in 1990 by DG3RBU and DL8MBT and serves as the extension for NetNode. It is able to have a maximum of 8 Channels with a maximum Baudrate of 19200, it is armed with ICs of the Type ^Z8530^. A User Version of the Card has been available since December 1991 and has 4 Channels with 3 Modems directly on the Card. \\SCC.EXE SCC.EXE Is the Terminal Program of BayCom. It is loaded after ^L2.EXE^, in order that the facilities of Packet-Radio-Capabilities are made available. Command Line Parameter: scc -c Clears the opening Screen with the Call -c scc -m uses minimum RAM Space. Through which more space remains for DOS-Usage (:OSHELL) (considered for the extension of NetNode) The Name of this Program comes moreover from the IC which is employed on the ^SCC-Card^ :- ^Z8530^-SCC. \\SCC.INI Default-Parameters are contained in the File SCC.INI. The File is extensively self explanatory and is able to contain all Operating Parameters. WARNING: With each alteration of SCC.INI SCC.PAR will be automatically cleared, consequently the Parameters that were changed from the Terminal only, will have been lost. Adjustments which have been made during the course of the running of the Program are therefore removed. Important changes that are made during operation and required to be retained should be entered into SCC.INI on exit from the Program. Almost all of the Parameters, which will be installed in SCC.INI are able to be altered while the Terminal is in use. Settings which contain the Initialisation Values, e.g. the choice of the Video-Adapter, are effective for the first time after the next Start of the Program! \\SCC.PWD SCC.PWD is the ^Password^-File of BayCom. It will be used both by ^BayComNode^, and also by the Terminal. The creation of a Password is similar to TheNet, i.e. it will demand through random numbers the appropriate Characters from an 80 Character position String. \\SCCBASE ╔═══════════════════════╗ SCCBASE <Address> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ The Address of an SCC-Expansion-Card is able to be installed with this Parameter. The declaration is able to be decimal or following a $ character, in hexadecimal. Possible Addresses for the User-^SCC-CARD^ are to be found in the USCC-Manual on page 40 . The Installation in ^SCC.INI^ must agree with the Jumper Position on the Card. Example: SCCBASE $300 (IO Prototype, mostly free) \\SCCINT ╔═══════════════════════╗ SCCINT <IRQ-Number> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ The Valid IRQ number that is able to be employed when operating with an ^SCC-CARD^. More precise information is able to be obtained from the USCC-Manual on Page 40. With Jumper position (JP2) it is able to switch between IRQ5 and IRQ7, dependent upon which is still free. Usually both Interrupts are free, there is a possibility that some Cards may make use of these Interrupts already. It should help in case of doubt to study the descriptions of all PC Expansion Cards in use, and also simple testing. \\SCREEN The Screen is divided into 3 Windows separated by two ^StatusLine^s containing important Operating Information. - Upper Window: Issue of Commands and Data. With the presence of a colon (ESC KEY Toggles) at the beginning of the Line, the Text will be interpreted as a Command to the Program. - Middle Window: Receiving Window. All incoming Data will be displayed here, which is intended for this Station and for which, an actual Connection exists. - Lower Window: Monitor. Here all incoming and transmitted Packets will be displayed. Switching and alteration of the Windows is described under ^KEYS^. \\SEND SEND <^BOARD^> @ <End Mailbox/^Distrib^utor> # <^Lifetime^> <Reference> This Command causes the sending of a Communication to the given Board. The Board Name is able to be that of a User-Board (therefore the Call Sign of the Receiver) or of a ^Bulletin^-^BOARD^. The End Mailbox issues, to which Mailbox the Communication has to be sent. Here therefore, Collective Names (e.g. DL) are possible. This Output is not valid for Communications to User-Boards (so called. personal Communications), therefore the System sends the Communication to the Standard Mailbox of the User, in so far as it is known (otherwise it seeks the Name of the End Mailbox). After '#' the Life Duration of the Communication is able to be sent to the End Mailbox(s) (only with Info-File/Bulletin-Boards). The Reference is the Communication title (max. 25 Characters long). All requisite Outputs, which are not given in the Command input, the Box requests explicitly. Consequently it to issue SEND and then answer the Questions which follow, if one is not yet so "experienced" After the issue of the Command the Box forwards to the Writer the Communication end. It is : - with DieBox-Systems: CTRL-Z or ***END - with DXL-Systems: CTRL-Z or \\SOFTWARE ╔═══════════════════════╗ SOFTWARE ║Command for ^BayComNode^ ║ ╚═══════════════════════╝ Gives out a Description of the Digipeater-Software (if loaded) \\SPEAK ╔═════════════════╗ SPEAK <Language> ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Command 'SPEAK' allows Text Output of the Mailbox to be switched into another Language. For:- <Language>, the current Language Character, see below. This is the Prefix-Allocation of the corresponding Country supported and a maximum of three digits. The Command given without, or with a false Language Character, causes the Box to give a List of the optional Languages. 'SP DL' ..........: Output Text in German Language; 'SP G' ...........: Output Text in English Language; 'SP F' ...........: Output Text in French Language; After switching and therefore with the next Log In the Box will Report in the chosen Language. \\SSID Secondary Station IDentifier. This is a Number that will used after a Minus sign to segregate and indicate the Call Signs that are able to be used in the Packet-Radio Operation. It is possible with this feature with one Call Sign and with separate Equipment or Functions to operate multi-Connects. Example: DL8MBT-12 SSID added to the Call Sign \\ST After repeated requests it is now possible to create Keyboard Macros. With the use of ALT-Letter or ALT-FKey a short Text or Command is able to be actioned. The Text will be handled as if it had been issued direct from the Keyboard. Digicom Users are already versed in this method, from which the Syntax has been taken. Declaration of a Text: :ST A Text Here A stands for a Letter or Number on the Keyboard, and the required Text follows. In the Example the Text will be Called by ALT-A For Multiple Line Texts the following gives an example: :ST A0 First Line :ST A1 Second Line etc. A Letter or a Numeral and a Line Number (0..9) is able to be co-ordinated for each Line. With this, it allows 36 Texts of 10 lines to be declared, which for most applications should be adequate. Longer Texts are sent more satisfactorily as a File from the Hard Disk or Diskette (^READ^). Contrary to Digicom practice, each line will be ended by a RETURN. The insertion of \i prevents the issue of RETURN An Overview of all stored Texts is obtainable by :^LIST^ From within the Standard Texts pre-prepared ^ST-Macros^ are able to be used, with whose help a limited utilisation of the Texts is possible. Functions which previously were already available with ALT- Keys (i.e. ALT-X and ALT-U see ^KEYS^) are able to be over- written by the declaration of new Texts and therefore no longer available. Additionally the Function Keys ALT-F1 to ALT-F10 are able to be utilised by Texts 0..9 (0 corresponds to F10). By using ALT-F1 the previous Function (Last Help) will be no longer available. Thought should be given to the use of: :ST X\x:SYSTEM\i Whereby after the pressing of ALT-X, RETURN must be pressed, in order to exit from the Program. It is unreservedly recommended that Standard Texts should be installed in ^SCC.INI^ and not entered from the Keyboard with SCC running. REASON: After the next run of PARA all alterations will be lost. :ST Z \z:connect \i \\ST-Macros From within Standard Texts, defined by ST (^ST^) it is able to define Special Functions. This stems from an Overview of prevailing Functions in SP from DL1MEN. \a :Time in HH:MM, length of time of a Connection \c :Call Sign of the Opposite Station \d :Actual Date inserted here \i :Prevents the automatic issue of RETURN \k :Port Number also Number of the Screen \l :Log-In Time at the beginning of the Connection \m :Own Call Sign \r :RETURN corresponding to Key RETURN (ENTER) \t :Immediate Time inserted \v :Version Number of the Software \w<Call> :Discontinues the Output of the Text until a Connect with the following Call Sign \x :Clears the Line containing the Cursor Example :ST C0 :c db0aab :ST C1 c db0rgb :ST C2 \w db0rgb :ST C6 c dg3rbu :ST M0 Hello \c, here is \m with BayCom Version \v, :ST M1 it is \t Time on the \d, Log In was at \l on Port \k \\STATUS ╔════════════════════════╗ STATUS ║ Command for ^BayComNode^ ║ ╚════════════════════════╝ Issues statistical information of the Node Software. Possibilities: Short Form. status gives the Statistics for the last Hour. S status all gives the Statistics since the Start of S A the Software. (Values will be measured and related to 1 Hour) status short gives only running Time and released in S S short form. The Report follows in the following Format: Ch : Channel Number, see also LINKS-List IntTx : Info Packets sent on this Channel Ack : Acknowledged Packets. The difference was lost %Ack : Per cent of the Acknowledged I-Packets Rout : I-Packets, which the Router has sent on this Channel Recv : I-Packets, which have been received on this Channel Lnk : Number of Connections on this Channel Max : max. Quantity of Connections since start of Software RxkB/TxkB : Quantity of sent and recv. Bytes on this Channel Baud : Baud on this Channel, on which the Balance covers The Channel 9 in the List is an internal Connection in the Software. Here runs e.g. Connections between Mailbox and Digi Every 5 minutes the Software sends a Beacon on the User Entry, with the following information. Links ... Number of the currently logged in Stations kB/h ... kBytes sent and received in the last hour RAM used ... Immediate occupied Buffer Storage in kByte Runtime ... Time in Hours:Minutes since the last Reset CALl:TT ... The average Answer time of all Direct Link Partners in 1/10 sec. Units. all Link partners. This Beacon serves in the first part for De-Bugging. In addition it is able to be seen without Connection to the Nodes, how good/bad the Interlinks are functioning at the moment. \\STATUSLINE - upper Status line: (Dividing line between TX- und RX-windows) mem= Quantity of free ^Buffer^ in the Free Store Chain ln= Possible 'Scrollable' Lines (RAM size dependent) n2= ^RETRY^- Retry Quantity (Residual Retries) o= Number of sent but not acknowledged Packets fr= Indicator of the immediate ^FRACK^-Time on this Link (Roundtrip-Delay) in 100ms-Units. k= Layer 1 ^Channel^ on this Port (only with ^SCC-Card^) Clock Time and actual Port number then follows. At the End of the Line stands the State of: I=Ins/R=Replace U=DIN-Umlaut (^GERMAN^) - lower Statusline: (Dividing line between RX- and Monitor-Window) Here all Ports and their Connected-Partners will be displayed. At the End of this line the Current File Send- or -receive position will be shown in Bytes. \\SUPPLIES The following are available from Rudi Dussmann, (DK5RQ) Otto-Hahn-Str. 9, 8400 Regensburg, Germany. Program with Instructions 20.00 DM RS232 Modem Kit incl TCM3105 & Software 89.00 DM RS232 Modem Ready Built & Software 125.00 DM Additional for Open Squelch Operation 10.00 DM Empty PCB with Construction Notes 12.00 DM Surface Mount Modem Kit 9 or 25 Pin Plug 94.00 DM Surface Mount Modem Ready Built 9 pr 25 Pin Plug 150.00 DM Empty SMD Modem PCBs with Construction Notes 12.00 DM USCC-Expansion Card with 2/3 Modems Please Enquire It is suggested that you Contact Rudi. either by letter or at DG0RBU for further details. \\SYSTEM :SYstem ends the Program. The Function corresponds exactly to the Key Combination ALT-X and is thought to be in the front Line for Remote Control. Naturally it is only sensible if the owner of the Station explicitly wishes it. It should NOT be freely allowed by use of ^RCMD^, but only be attainable by using a ^Password^ first. It is sensible that the application is actually used with the inclusion in a NetNode. With this method and through an endless Loop in the AUTOEXEC.BAT, the Software is able to be reset or a newly loaded re-start enabled. \\TAIL TAIl <Channel> <10ms-Value> TXTAIL. Time, which is allowed to expire after no more Data has been submitted for transfer, before switching off (PTT) the TX Full-Duplex-Connections (only with ^SCC-Card^) and Modems with 'long conductance' (e.g. 7911, Value approx. TA 3) The Qualifier <channel> is only relevant when using an ^SCC-Card^ \\TALK ╔═══════════════════════╗ TALK ║Command for ^BayComNode^ ║ ╚═══════════════════════╝ With this Command the Converse Mode is obtained. Possible applications are: t <call> ....text..... ; Text sent to Station <call> t <call> (without Text) ; Everything issued sent to <call> t <number> ; switch to Converse ring <number> See additionally HELP ^CONVERSE^ \\TBUFFER TBuffer <Quantity> The quantity of ^Buffer^-Blocks, that is able to be held in RAM during sending of Data. Especially with the sending of Files it is independent of the setting of ^MAXFRAME^, possible to hold a definite quantity of Data in the RAM, e.g. during the course of short time pause of BayCom Terminal the Data will be sent continuously. The Quantity of the Buffer Store indicates Units of 330 Bytes (this devious Value is produced from the max. Length of a Packet) and should be set to lie at least in the order of the magnitude of MAXFRAME. \\TELL ╔═════════════════╗ TELL <BoxCall Command> ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Command 'TELL' allows quasi a distant request of other Mailboxes. It is able to be sent with Commands to a Box. This will be executed and the result will be returned by S&F. Example: TELL DK0MAV DIR ALL That User- and Info-Index of DK0MAV will be per S&F executed and per S&F returned. The interactive Commands such as SEND, MYBBS, NAME, BELL are not possible. TELL functions only if the End Mailbox is able to recognise this Command. This is possible by DIEBOX from Version 1.6! \\TERM-COMM Commands for BayCom-Terminal (see also ^TNC-COMMAN^DS): ^ANSWER^ Personal CTEXT ^CBELL^ Piep for Con/Disc ^CLEAR^ Screen Clearance ^COMMAND^ Colon Toggle ^CRTSAVE^ Screen Blanker ^CTEXT^ Connect-Answer Text ^ECHO^ RX to TX Screen ^EDIT^ Edit Text File ^ENGLISH^ Eng/Germ. Report ^EXITLOG^ Update at Prog. End ^GERMAN^ DIN or IBM Chars. ^HELP^ Output Help ^INFO^ Send Info. ^KNAX^ Noise from RX ^L2CTEXT^ CT without SCC ^LIST^ Standard Text List ^LOG^ Log Book ON/OFF ^MHEARD^ Call Signs Heard ^OSHELL^ Shell to DOS ^QTEXT^ Text sent by QUIT ^RCMD^ Allowed Rem. Ctrls. ^READ^ Send Text File ^REMOTE^ Rem. Ctrl. ON/OFF ^RPRG^ Send Binary File ^SATTRIB^ Colour installation ^SAVEPORTS^ Screen Saved ^ST^ Create Std. Texts ^SYSTEM^ Program End (ALT-X) ^VERSION^ Switch on Report ^VIEW^ File shown on Screen ^WPRG^ Binary File receive ^WRITE^ Text File received \\TERMHELP TERMHELP.SCC The File containing the Help Text for the BayCom-Terminal. It is able to be altered and extended with any favourite Text Editor, of course there are strict Rules for the construction of the File which must be observed. After each alteration, ^PARA.EXE^ must be called by the Form para -h, in order to create a new index. That left undone, nothing will be guaranteed... Eventual appearance of Warnings and Advice should be taken seriously, otherwise the viewing of the Help Text will be capable of being an awful mess. \\TheNet This NetNode software stems originally from the USA and is being distributed there commercially under the Name NET/ROM. It runs on TNC2-Hardware usually obtained from Trade suppliers and offers limited ^AutoRout^ing. The Software has been modified further by OMs of the Nord><link-Group and will be distributed predominently under the Name 'TheNetNode' for IBM-PC and Atari ST Hardware. Overview of possible Commands: (Usable short form in Brackets) Follows on the Next Pages. (A)ktuell shows New Items relating to the respective Nodes (C)onnect conducts the Connection Construction to the respective given Call or End Node. The individual ^NetNode^ of the TheNet-Net contains an Autorouter, i.e. every Node is known to every other Node, the Connection Construction is able, without indication and knowledge of the individual intermediates, to be ensured to the end. If a Station is not known, it will be sought; to create the connection from the User's Entry Command (CO)nvers sets up the ^Converse^-Mode, the issue of a "Circle Number" is possible to be attached. Using /? or /help is able to request further Info about the individual available Commands. CQ <text> CQ-Call on the User Frequency (HA)rdware issues Hardware Description (H)ilfe shows a Short List of the Commands (I)nfo short Station Description (L)inks shows the collective neighbouring Nodes (M)ap Sketch Map of the locality with the Neighbour Nodes (MH)eard shows a List of Nodes which were heard on the User Frequency (N)odes Node lists: Lists of the known NetNodes (P)ath <Call> issues the Path to the given <Call> (Q)uit Connection to the Node will be cut (Disconnect) (R)outes Distribution of existing Nodes (SO)ftware Issues short Information on the Software in use. (S)tatistic shows Number of the sent and received Bytes, Token Count, Disturbance etc. (TE)st issues a 4kB length sequence from 0/1, to be able to usefully equalise the ^Modem^ (T)ime Issues System Time and Date (U)ser Shows the Users, currently using the Node. \\TIME ╔═══════════════════════════════╗ TIME ║ Only for ^DXL-Box^ & ^BayComNode^ ║ ╚═══════════════════════════════╝ gives the actual Clock Time (mostly UTC) \\TINFO :TInfo <100ms-Value> Info-Timer. Only Valid from the User Interface (SCC.EXE), it is the Time which is allowed for the Frames to be packed, after which no more Info will be written to the Buffer. With an explicit Press of the Return Key the Info will be sent immediately. \\TNC-COMMAN Collected Commands for BayCom L2 (see also ^TERM-COMM^ands): ^BADRESS^ Beacon Call Signs ^BEACON^ Beacon Time ^BTEXT^ Beacon Text ^CNOT^ Con. barred List ^CONNECT^ Connect Construction ^CSTATUS^ List of Connects ^DAMA^ Collision Avoidance ^DCALL^ Digipeater Call ^DISCONNECT^ Saver a Connection ^DISCTIME^ Connect-Timeout ^DWAIT^ Channel free wait ^FRACK^ Wait Time Retry ^HBAUD^ Baudrate ^IPOLL^ Info-Poll Length ^KANAL^ Modem Chan. Sw. ^LINKTIME^ Connection Check ^MAXFRAME^ Unacked Frames ^MBUFFER^ Mon-Buff. Length ^MCALLS^ Monitor-Call Sign ^MHEADER^ Line Feed in Mon. ^MONITOR^ Monitor-Channels ^MSELECT^ Mon.-Selection ^MYCALL^ Own Call Signs ^PACLEN^ Max. Packet leng. ^QUIT^ Sever a Connection ^RESPTIME^ Answer Delay ^RETRY^ Max. Retries ^TAIL^ Frame-End Flags ^TINFO^ Info-Delay ^TQUIT^ Quit-Timeout ^TXDELAY^ Frame-Start-Flags ^XCONNECT^ C other MYcall \\TQUIT :TQuit <10sec-Value> Quittimer, severs the Connection after a :Q, ALSO IF Data still remains. This Time should be thought of as a Timeout, with it hopeless Connections or, if no more Data passes over the Channel the Connection can be terminated. :\\TRANSFER ╔═════════════════╗ TRANSFER Rubrick No. > End Rubrick ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Command 'TRANSFER' executes the reverse Copying of Communications. The issue of '>' is unquestionably necessary! TRANSFER then is only applicable, if Source- and End-File are the same Type: User-File --> User-File and Info-File --> Info-File. The transformation of an Info-Files into a User-File or the reverse is NOT possible! With the Transfer of an Info-File the source will be erased, but not with the Transfer of User-Files. Example: TRANSFER DF3AV 3 > DL2YAP With this Command it is possible, to write the same Communication to different Users, without the need to repeat. If this Communication is to be forwarded to a certain User, then the FORWARD-Command is to be used. Details for this purpose see under 'HELP FORWARD'. \\TXDELAY TXdelay <Channel> <10ms-Value> Time between the Keying of the TX (PTT) and the sending of Data to the TX. This Time serves to Compensate for any slowness of the Sender and/or the Receiver, but should be set continuously as SMALL as possible. The setting is in 10ms-Units. Reasonable Values lie between 12 and 25. The OutPut <channel> is only relevant when using an ^SCC-Card^ \\UNPROTO The Command UNPROTO does not exist in BayCom. Generally however, Data will be able to be sent only on Port 0 (accessible with F10) from where no Connect is possible, the ^CONNECT^-Command will be used for the setting of the Unproto Address. A Connect will be internally executed, which of course will not lead to an actual Connection. The Data will be sent as UI,P (un-numbered Info with Poll). The set Poll-Bit also has the benefit, that it is able to be issued for Test purpose. In accordance with AX.25 it has to react with a DM,F to UI-Frames with Poll, therefore it is able to be observed on the Monitor. This Method will be employed for example, on ^Flexnet^ with the FIND-Command for the search for Stations. \\USAGE ╔═════════════════╗ USAGE (call) ║ Only for ^DieBox^ ║ ╚═════════════════╝ The Command 'USAGE' calls for the Output of a Log Book or for the Output of Information about a particular User. a) after the issue of 'U' the Mailbox issues the following Lines: LOGINs: 1:HB9CMT 2:HB9SBS 3: 4: 5:DG7GF 6: 7:FD1MAP 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: It will be simply the logged Call Signs shown. b) after the issue of 'U DF3AV' the Mailbox issues e.g.: Call : DF3AV Name : REINHARD Language : DL MyBBS : DK0MAV LastLogin : 15.06.88 03:37 \\USERS :Users ) or ) Commands are interchangeable :CStatus ) issues a List of the immediate connected Stations. Example: Port Status Call 1 Info Transfer DL8MBT > DB0AAB 2 Link setup DL8MBT-2 > DG3RBU \\User-Routi User-Routing Name of the ability of a ^NetNode^, to find a particular User in the Packet-Radio-Net. With the ^DXL-Gate^ the User must with the issue of the MYLAN Command obtain for himself, where the station has last been heard. The ^BayComNode^ MH-List contains the Upward Digis of the last 2047 Stations, which have passed through these Nodes in the course of Connections. A Connect Request can now be made from Information obtained. This Routing does not function in a ^TheNet^ locality. \\VADAPTER VAdapter <videocard> designates the Type of Video-Output employed. The following Values are possible: 0 automatic recognition of the Video Card. Toggles between Monochrome and Colour. If EGA or VGA is discovered, there follows a switching into 43, 50 or 60-Line Mode. 1 Monochrome-Video (MDA, Hercules) Video-RAM at B000h! 2 Colour-Output 80x25 Lines with CGA, EGA, VGA 3 LCD-Output (as 0, but Black & White Settings) An alteration is only available after a re-start of the Programs. \\VERSION VERsion Displays the Version Number of the Software. Additionally it will be shown to QSO Partners. \\VIEW :View <filename> Places the Data from the File on the Screen for examination. Only Text Files will be able to be viewed. The Data will be displayed in the RX Window (middle). An interruption of the Output is possible by means of the SHIFT-TAB (see also ^KEYS^). \\VCOLUMNS ╔═══════════════════════╗ :VColumns <Quantity> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ Video-Aperture. This Parameter normally stands on 80, because the usual Video Card outputs 80 Characters per Line. Should the installed Video Mode be required to be other that an Aperture of 80 then this is the Parameter to be altered. (before the Start of ^SCC.EXE^) Cross Reference: ^VLINES^ ^WWRAP^ \\VLINES ╔═══════════════════════╗ :VLines <Quantity> ║ Only valid in ^SCC.INI^ ║ ╚═══════════════════════╝ Screen-Lines. Here the Quantity of Lines will be set that will be available for the Video-Output. A re-adjustment for the EGA/ VGA Video Modes is not required, this will be interrogated and set automatically. Consequently the adjustment is only effective if no automatic switching of the Video Mode occurs. Normally the Output stands at 25 Lines, but it is able to be enlarged, if BEFORE the Start of ^SCC.EXE^ the Video Output has been switched to another Display. Cross Reference: ^VCOLUMNS^ \\WPRG :WPrg <filename> Saves a binary Program to the Disk. The Data will be received transparent, it follows therefore, that there will be no recognition of the beginning and end of a File, this must be self activated. Remote Control during the receiving of binary Data is blocked. The individual Command function //WPRG OFF must also be given. To be observed is, that before the Command there must be a Line Feed issued (Return-Key), which customarily is not the case at the end of binary Data Files. \\WRITE :Write <filename> Saves the incoming Text to the Disk. Ended with the Issue of :WRITE OFF The Customary Packet Radio CR will be transformed into the usual DOS CR LF. In addition: the ^GERMAN^ ON the German Umlaut will be changed from the DIN-Character Set into the IBM-Character Set. \\WWRAP :WWrap <position> Word-Wrap: an automatic Line Feed. This Parameter is the actual Position on the line after which, a word will be moved into the next Line, no more being allowed. The Line length is normally 80, and for that reason this Parameter should be installed with this Value. A variation is sensible, if the Output from the QSO-Partner is narrower, but mostly an alteration is normally not necessary. Cross Reference: ^VCOLUMNS^ ^VLINES^ \\XCONNECT :Xconnect <mycall> <call> [ <digi> ... ] Connect with one of the first MYcall dissimilar Calls, therefore Outward Connection under an optional Call Sign. Example: :x dl8mbt-6 db0rgb db0aab Here DL8MBT-6 will build a Connection to DB0RGB via DB0AAB It is also possible for a visiting Amateur (G1***) to use the System of G?*** by the following: :X G1*** GW+++ <digi> etc It will be recorded in the Log as G1*** making the Call to GW+++. \\Z8530 Z8530-SCC (SCC = Serial-Communications-Controller) is employed in the Node-Version ^HDLC^-Controller, which is on the Expansion Card: ^SCC-Card^ for the IBM-PC. This IC is able to control 2 Modem Channels and takes over the Lowest Level of the Packet-Radio-Operation. That is, the fundamentals of the process of the Data cycle. Building and Decoding of the different parts of the Code so that the In- and Out direction of Null bytes for certain self regulation. In addition the IC calculates a Check sum from a Cyclical Redundancy Code (CRC), which with given Redundancy of 16 Bits, is the best possible choice for Error Recognition. From the nomenclature of this IC comes the Program Name ^SCC.EXE^